Session 1.4 – What is a Team?
Chapter 2: The Logic of the Team Software Process | Duration: 1 hr
Learning Objectives
By the end of this session, students will be able to:
- Define what constitutes a team using formal criteria
- Understand optimal team size for software development
- Explain the concept of a "jelled team" and its characteristics
- Identify the three basic conditions required for effective teamwork
- Distinguish between groups and true teams
Introduction
Before discussing how to build and manage teams, we must first establish a clear understanding of what a team actually is. Not every group of people working together constitutes a true team. Teams have specific characteristics and requirements that differentiate them from simple working groups.
Why Definition Matters
A precise definition of "team" is essential because:
- It helps us understand what we're trying to build
- It provides criteria for evaluating team effectiveness
- It distinguishes true teams from collections of individuals
- It guides the design of team processes like TSPi
Key Point: Teams are not just groups of people assigned to work together. True teams have specific structural and behavioral characteristics that enable them to achieve results beyond what individuals could accomplish alone.
Defining a Team
There are many definitions of teams in the literature. For TSPi, we use the definition provided by Dyer, which captures the essential elements of teamwork.
Formal Definition of a Team
A team consists of:
(a) At least two people, who
Teams require multiple individuals. A single person cannot form a team, as teamwork requires interaction and collaboration between people.
(b) Are working toward a common goal/objective/mission, where
Team members share a unified purpose. They are not pursuing individual, separate objectives but are collectively focused on achieving the same outcome.
(c) Each person has been assigned specific roles or functions to perform, and where
Team members have defined responsibilities. Everyone knows what they are supposed to do and what others are doing.
(d) Completion of the mission requires some form of dependency among the group members
Team members need each other to succeed. The work of one person depends on or contributes to the work of others. No one can complete the mission alone.
Source: Dyer, page 286
Understanding Each Criterion
At least two people - This seems obvious, but it establishes the minimum size. While teams can have two members, most effective software teams have more.
Why it matters: Teamwork skills - communication, coordination, compromise - only exist when multiple people interact. Individual work, no matter how excellent, is not teamwork.
Working toward a common goal/objective/mission - All team members must share the same end objective. They are not working on separate, unrelated tasks.
Team Example
Five engineers building a student registration system - all focused on delivering a working product.
Not a Team
Five engineers each building separate projects for a class - working in the same room but with different goals.
Each person has been assigned specific roles or functions - Team members have clear, defined responsibilities. This reduces confusion and ensures all necessary work is covered.
In TSPi:
- Team Leader - Coordinates team activities and manages meetings
- Development Manager - Tracks development progress and product quality
- Planning Manager - Manages schedule and resources
- Quality/Process Manager - Ensures process compliance and quality standards
- Support Manager - Handles configuration management and tools
Completion of the mission requires some form of dependency among group members - This is the defining characteristic of true teams. Members must rely on each other.
Interdependency in Software Teams
Team members depend on each other's work to achieve the common goal
Example: A developer cannot implement features without a design. A tester cannot validate functionality without requirements and working code. Each role depends on others to complete the project successfully.
Team Size
Teams can theoretically be of almost any size from two to dozens or even hundreds of people. However, team size significantly impacts effectiveness, communication, and cohesion.
Team Size in Industry
In practical industry situations, teams are most effective when they develop close relationships among all members. This is most likely when:
- The teams are small
- The members develop a network of interdependencies
- Everyone knows everyone else's work
Industry Practice: Team size is generally limited by management span of control. Although some projects can be very large, generally there are smaller subgroups of 20 or fewer people, each working under the direction of a supervisor or manager. These subgroups form the close-knit teams that the TSP and TSPi are designed to support.
Team Size for Student Teams
Typical Range
4-12
Students per team, depending on class size and faculty preferences
Optimal Range
4-8
Engineers - most likely to be effective based on experience
TSPi Design
5
Students - TSPi is specifically designed for teams of five
Team Size Trade-offs
- Insufficient Coverage: Not enough people to properly handle all the team role assignments
- Limited Skills: May lack necessary skill diversity
- Overload Risk: Each person has too many responsibilities
- No Redundancy: Illness or departure severely impacts team
- Harder to Jell: Difficult to develop close relationships needed for teams to jell
- Communication Overhead: Exponential increase in communication paths
- Coordination Challenges: More complex scheduling and coordination
- Free Rider Risk: Easier for members to hide lack of contribution
TSPi Flexibility
Although TSPi is designed for teams of five students, it can be adapted:
- Teams of 4 or 6: Can be used with modest role assignment changes
- Other sizes: Require more significant role adjustments, but the other scripts and forms still apply
- The five TSPi roles provide good coverage for team activities while remaining manageable for a small team
The Jelled Team
When design and development groups work together smoothly and efficiently, we call them jelled teams. This concept, popularized by DeMarco and Lister, represents the highest level of team performance.
Definition: Jelled Team
From DeMarco and Lister's book Peopleware:
"A jelled team is a group of people so strongly knit that the whole is greater than the sum of the parts. The production of such a team is greater than that of the same people working in unjelled form. Just as important, the enjoyment that people derive from their work is greater than what you'd expect given the nature of the work itself."
Source: DeMarco and Lister, Peopleware, page 123
Characteristics of Jelled Teams
Enhanced Performance
- Production greater than sum of individual capabilities
- Synergistic collaboration
- Efficient problem-solving
- High-quality output
Increased Enjoyment
- Members enjoy their work
- Strong sense of camaraderie
- Mutual support and respect
- Pride in team accomplishments
Strong Cohesion
- Tightly knit group identity
- Shared values and goals
- High level of trust
- Effective communication
Smooth Operation
- Work flows smoothly
- Minimal friction or conflict
- Self-organizing behavior
- Adaptive to challenges
The Jelling Process
Teams don't become jelled overnight. Jelling is a process that happens over time as team members work together, build trust, develop shared understanding, and align on common goals. TSPi accelerates this process by providing structure and practices that facilitate team jelling.
Basic Teamwork Conditions
Not all groups are teams. There are three basic conditions that must be met for a group to operate successfully as a team. These conditions provide the foundation upon which effective teamwork is built.
Critical Foundation
Without these three basic conditions, a group cannot function as an effective team, regardless of how talented or motivated the individual members might be. These conditions must be established at the start and maintained throughout the project.
Clear and Distinct Tasks
The tasks to be done are clear and distinct
What This Means:
- The job for the team is explicitly defined
- The work is meaningful to the team
- The group knows what it must do
Why It Matters:
Without clear tasks, team members don't know what to work on, can't coordinate effectively, and waste time in confusion. Clear tasks provide direction and focus.
Team is Clearly Identified
The team is clearly identified
What This Means:
- Members know the scope of the group
- Who is in it and who is not
- Everyone on the team is known to the others
- Everyone's work is visible
- Everyone knows everyone else's team role
Why It Matters:
Clear team boundaries create accountability, enable effective communication, and build trust. Members must know who they're working with and what each person does.
Team Has Control
The team has control over its tasks
What This Means:
- Members know what to do
- Members know how to do it
- Members know when to do it
- Members know when they are finished
- Members know they are responsible for the work
- Members control the processes they use
- Members have the capability to do the job
- No one else is charged with doing it
Why It Matters:
Control empowers the team to manage their work, make decisions, and take ownership. Without control, the team becomes passive and dependent on external direction.
How TSPi Establishes These Conditions
| Condition | How TSPi Provides It |
|---|---|
| Clear Tasks | Requirements definition, design specifications, task planning, and explicit work assignments make tasks clear and distinct. |
| Clear Team | Team formation in launch, defined roles (Team Leader, Development Manager, Planning Manager, Quality/Process Manager, Support Manager), and visible work tracking ensure everyone knows the team composition and roles. |
| Team Control | Self-directed teams create their own plans, choose their processes, track their own progress, and make their own decisions within the TSPi framework. The team owns the work. |
Research Foundation
These three basic conditions are drawn from extensive research on team effectiveness by Cummings, Dyer, and Mohrman. They represent the minimal structural requirements for a group to function as a team, regardless of the specific domain or industry.
Sources: Cummings, page 627; Dyer, page 286; Mohrman, page 279
Session Summary
Key Takeaways
A team must have:
- At least two people
- Working toward a common goal
- With assigned specific roles
- With interdependency among members
- General: 4-8 engineers most effective
- TSPi Design: 5 students
- Too small (< 4): Insufficient role coverage
- Too large (> 8): Harder to jell
The Jelled Team
A group so strongly knit that the whole is greater than the sum of the parts, with production and enjoyment both exceeding individual work.
Three Basic Teamwork Conditions
- Clear and Distinct Tasks: Team knows what must be done
- Team is Clearly Identified: Members know who is on the team and their roles
- Team Has Control: Team controls how, when, and by whom tasks are done
Next Session Preview
In the next session, we will explore Building Effective Teams. We'll examine the four essential elements that transform ordinary groups into high-performing teams: cohesion, challenging goals, feedback, and a common working framework.