23 Working Effectively In Teams

CONTENT

  • Why Teams Matter
  • Building Trust
  • Accountability
  • Working Through Conflict
  • A Final Thought

Key Points

  • Why software design depends on effective teamwork.
  • How trust supports collaboration, honesty, and shared problem solving.
  • Why accountability matters for fair and reliable team work.
  • How to approach conflict constructively rather than avoiding it.
  • Why respectful communication helps teams work through uncertainty.

Why Teams Matter

Very little software is built alone.

Modern software projects depend upon people with different backgrounds, experiences, and expertise working together.

The strongest teams are not those with the smartest individuals.

They are the teams that communicate effectively.

Building Trust

Trust develops slowly.

It grows when teammates:

  • keep commitments,
  • communicate honestly,
  • admit mistakes,
  • ask for help,
  • support one another.

Trust allows people to contribute ideas without worrying about being embarrassed.

Accountability

Accountability is not about blame.

It is about reliability.

Your teammates should be able to depend on you. When something changes, communicate early.

Small problems become large problems when people stop communicating.

Working Through Conflict

Disagreement is inevitable.

In fact, disagreement often leads to better software.

The important question is not whether teams experience conflict.

The important question is how they respond.

Healthy teams challenge ideas. Unhealthy teams attack people.

Focus conversations on the design – not the designer.

Giving And Receiving Feedback

Good feedback is:

  • specific,
  • respectful,
  • actionable,
  • timely.

Likewise, receiving feedback requires openness.

Someone pointing out a weakness in your prototype is helping improve the software – not criticizing you personally.

While you can provide feedback to your peers at any time, you’ll formally provide feedback after you have completed each Lab Demo. You’ll do this through our course website. If you’ve never provided feedback before, check out the following video.

 

Psychological Safety

Psychological safety means people feel comfortable:

  • asking questions,
  • admitting uncertainty,
  • suggesting ideas,
  • making mistakes.

Innovation happens when people feel safe enough to experiment.

A Final Thought

Software is built by people for people.

The quality of your relationships often influences the quality of your software.

Learning to work well with others may become one of the most valuable skills you develop in CIS3750.

 

Building Effective Teams. Effective teams develop through shared goals, trust, accountability, communication, organization, feedback, respect, and constructive conflict resolution. These practices help diverse team members work together, learn from different perspectives, and create stronger solutions. [Alt-text: Infographic titled “Chapter 23: Building Effective Teams.” A diverse group of five CIS3750 students collaborates around a laptop at the centre. Eight characteristics of effective teamwork surround the students in a circle: Shared Goals, aligning the team around common goals and celebrating progress; Trust, trusting each person to contribute and do their best; Accountability, taking ownership of work and following through on commitments; Organization, planning work, managing time, and staying organized; Feedback, giving and receiving feedback that supports growth; Conflict Resolution, addressing disagreements early and working toward solutions together; Respect, valuing one another, their ideas, and their differences; and Communication, communicating clearly, listening actively, and keeping everyone informed. The infographic concludes with the message, “Strong teams. Better solutions. Greater impact.”]

 

License

Software Design: Planning Purposeful Solutions Together - A Community-Engaged Approach Copyright © 2026 by Daniel Gillis; Nicolas Durish; and Alessandro Arezza. All Rights Reserved.

Share This Book