Session 1.5 - Building Effective Teams

Chapter 2: The Logic of the Team Software Process | Duration: 1 hr

Learning Objectives

By the end of this session, you will be able to:

  • Explain the four supports effective teams need: cohesion, goals, feedback, and a common framework
  • Describe how teams jell over time through convergence on goals, product understanding, and process
  • Show how TSPi guides goal-setting, role assignment, planning, and communication to build teams
  • Identify how visibility and feedback reduce shirking and improve commitment
  • Apply communication practices (internal and external) that keep teams aligned under pressure

4

Key supports needed: Cohesion, Goals, Feedback, Framework

Challenging

Goals must be specific, measurable & challenging

Visible

Performance feedback must be frequent and visible

Weekly

Regular meetings and tracking maintain alignment

Introduction

To build effective teams, you need more than just the right kinds of tasks and working conditions. The team must have an important job to do and must be in an environment that supports teamwork. The team must face an aggressive challenge and must be encouraged to plan and manage its own tasks.

"After setting the right conditions (clear tasks, identified team, control of work), teams need additional support to jell: cohesion, challenging goals, frequent feedback, and a common working framework."

— Chapter 2, Section 2.4

TSPi operationalizes these supports through roles, scripts, planning discipline, and communication practices. This session explores the four essential supports that transform groups into jelled teams.

The Four Supports for Effective Teams
Software Team Team Cohesion Tight knitting Unified group Challenging Goals Specific & measurable Significant challenge Feedback & Visibility Frequent & precise Individual & team level Common Framework Clear path to goals Agreed process

Figure: Four essential supports that enable teams to jell and perform effectively

Team Cohesion

Cohesion refers to the tight knitting of team members into a unified working group that physically and emotionally acts as a unit. Members of highly cohesive groups communicate freely and often. Although they need not be good friends, they work closely together and respect and support one another.

Cohesive vs. Non-Cohesive Teams
Non-Cohesive Team Indiv. Indiv. Indiv. Indiv. • Individual goals • Limited interaction • No common values Cohesive Team M1 M2 M3 M4 • Shared goals • Frequent interaction • Common values

Figure: Characteristics of non-cohesive versus cohesive teams

What Cohesion Looks Like
  • Shared Space: Common physical/virtual space and frequent interaction
  • Cooperation: Willingness to compromise and support teammates
  • Common Values: Aligned priorities and shared team culture
  • Interdependence: Work depends on each other, not isolated tasks
TSPi Enablers
  • Role Clarity: Reduces conflict over responsibilities
  • Regular Meetings: Keep relationships active and aligned
  • Shared Plan: Build trust in commitments and timelines
  • Peer Pressure: Encourages mutual support and accountability
Key Insight

In less-cohesive groups, members tend to function as individuals. They have trouble compromising and do not have common values and goals. Cohesive teams, however, share a common physical space, spend a lot of time together, and supportively cooperate and interact during these times together.

Challenging Goals

Goals are a critical element of the jelled team. Teams jell around meaningful, measurable, and challenging goals. Goals need to be specific enough to track and accepted by every member.

"No team jells without a performance challenge that is meaningful to those involved. Although good personal chemistry and the desire to become a team can foster teamwork values, these characteristics alone will not automatically produce a jelled team."

Three Requirements for Effective Goals
1 Specific & Measurable Examples: • Detailed plans • Quality targets • Schedule milestones • Defect rate < 5/KLOC • 100% code review 2 Significant Challenge Purpose: Motivates team jelling and extraordinary effort Trivial goals don't inspire; impossible goals demoralize. 3 Visibly Tracked How: • Progress dashboards • Weekly status reports • Burndown charts • Visible to all members

Figure: Three essential requirements for team goals that enable jelling

Goal Principles (Chapter 2)
  1. Specific and Measurable: Studies show that teams with measurable goals are consistently more effective than those that do not. Examples: detailed plans, performance targets, quality objectives, schedule milestones.
  2. Significant Challenge: Goals must represent a meaningful challenge to those involved. This motivates team jelling and sustains energy.
  3. Visibly Tracked: Progress must be displayed so team members can see how they are progressing toward their goals.
  4. Member Acceptance: Each team member must accept these goals as his or her own.

Feedback & Visibility

Goal tracking and feedback are critically important. Effective teams are aware of their performance and can see the progress they are making toward their goals. Frequent, precise feedback improves performance and reduces shirking.

Research Finding

In a study of air defense crews, those with frequent and precise feedback on goal performance improved on almost every criterion. This compares with the stable, unimproving performance of crews that did not get feedback.

The Shirking Problem

Team members must be able to distinguish their personal performance from that of the team as a whole. When they cannot do this, team performance generally suffers. This phenomenon is called shirking.

Feedback Reduces Shirking
Without Visible Feedback Team Performance Tracked (But individual contributions hidden) Shirking Occurs • Reduced personal effort • "Someone else will do it" • Lack of personal commitment • Team goals not internalized With Visible Feedback Team + Individual Tracked (Everyone sees their contribution) Full Commitment ✓ Maximum personal effort ✓ Personal accountability ✓ Strong commitment to goals ✓ Team goals internalized

Figure: How visibility of individual contributions prevents shirking

Key Insight

The basic cause of shirking is the lack of a team member's personal commitment to the team's common goals. The presence of one or more shirkers generally prevents a team from jelling. Shirking is not primarily a measurement problem, but precise measures generally reveal such problems so that the team can deal with them.

Why Feedback Matters
  • Shows Progress: Highlights progress toward goals and identifies risks early
  • Discourages Shirking: Makes individual contributions visible to all
  • Enables Help: Timely help requests when variance appears
  • Improves Performance: Teams with feedback improve; those without stagnate
TSPi Practices
  • Weekly Meetings: Status and variance tracking for all members
  • Dual-Level Measures: Time/defect/size at individual AND team levels
  • Visible Dashboards: Progress charts visible to entire team
  • Instructor Reports: External reports for timely support

Common Working Framework

Teams need to agree on how to achieve their goals: the tasks, order, owners, and completion criteria. Clear process reduces ambiguity and conflict.

Framework Element What Teams Need TSPi Mechanism
Tasks & Order Know what to do, when, and in what sequence Scripts with entry/exit criteria; cyclic strategy and planning
Roles & Ownership Clarity on who does what and authority to act Defined roles (leader, planning, quality/process, development, support)
Completion Criteria Shared definition of done and quality bars Standards, inspections, and checklists from PSP/TSPi

How Teams Develop

Teams typically start with diverse views and converge through iterations on product understanding and process. Conflict and confusion are normal parts of this convergence.

Convergence Pattern
  • Agree on the product goals and key unknowns
  • Iteratively resolve disagreements and clarify design/requirements
  • Converge on detailed plan and process while product understanding tightens

Source: Chapter 2, How Teams Develop and How Teams Jell

Communication

Communication is the most common team problem. Lack of status awareness blocks coordination and hides issues until late.

Internal
  • Weekly meetings to review status, risks, scope changes
  • Shared measures for crisp updates (time, defects, size)
  • Defined roles streamline who communicates what
External
  • Weekly summary reports to instructor/management
  • Show progress and ask for targeted help early
  • Maintain visibility to avoid surprises and build trust

Summary

  • Teams need four supports to jell: cohesion, challenging goals, frequent feedback, and a common framework.
  • Visible measures and weekly cadence reduce shirking and surface help needs early.
  • TSPi supplies structure via roles, scripts, planning, inspections, and communication norms.
  • Team development is iterative—conflict and clarification are normal steps toward convergence.
  • Consistent internal and external communication keeps alignment and secures timely support.
Previous Session Course Home