Agile guide · Agile roles and teams
What Is an Agile Team? Roles, Size and Characteristics
An Agile team is a small, stable, cross-functional group of people who together have all the skills needed to turn backlog items into finished, usable results. The team, not a manager, decides how to do the work.
Key takeaways
- Agile teams are small, stable, cross-functional and self-managing.
- Core roles are Product Owner, Scrum Master or coach, and Developers.
- Keep teams small to keep communication fast.
Characteristics of an Agile team
- Cross-functional: it includes every skill needed to deliver, so work doesn't wait for handoffs to other departments.
- Self-managing: the team decides who does what and how.
- Small: typically ten people or fewer; Scrum recommends ten or fewer in total.
- Stable: members stay together long enough to learn to work well together.
- Dedicated: members focus mainly on this team's work.
- Accountable together: the team succeeds or fails as a unit.
Typical roles
| Role | Responsibility |
|---|---|
| Product Owner | Maximises value; owns and orders the backlog; represents customers and stakeholders |
| Scrum Master or Agile coach | Helps the team use Agile effectively and removes impediments |
| Developers / team members | Plan and do the work; ensure quality; deliver the increment |
In Scrum, "Developers" means anyone doing the work, including designers, writers, testers and analysts, not just programmers.
Agile team vs traditional project team
| Traditional team | Agile team | |
|---|---|---|
| Structure | Specialists in functional groups | Cross-functional unit |
| Work allocation | Assigned by a manager | Pulled by team members |
| Lifetime | Formed for a project | Long-lived; work comes to the team |
| Focus | Completing tasks | Delivering outcomes |
Why size matters
The number of communication channels grows quickly with team size: a team of n people has n(n−1)/2 channels. Five people have 10 channels; ten people have 45. Small teams communicate faster and coordinate more easily. When work needs more people, split into several teams; see Scaling Agile.
Building a strong Agile team
- Agree a team charter or working agreement: hours, communication norms, how decisions are made.
- Develop T-shaped skills: deep in one area, able to help in others.
- Protect the team from constant reprioritisation.
- Celebrate team results rather than individual heroics.
- Invest in retrospectives.
Free templates for this topic
Frequently asked questions
What is the ideal Agile team size?
Most guidance suggests three to ten people. Scrum Teams are typically ten or fewer, including the Product Owner and Scrum Master.
Can someone be on several Agile teams?
It is possible but costly. Switching between teams reduces focus and slows everyone down, so aim for each person to belong mainly to one team.
What is an Agile team?
A small, stable, cross-functional group that has all the skills needed to deliver value and manages its own work in short cycles.
What does cross-functional mean in an Agile team?
The team includes every skill needed to finish its work, such as design, development, testing and analysis, so it does not wait on handoffs.
What does self-managing mean in an Agile team?
The team decides who does what, when and how, within the goals and boundaries set by the organisation.
What roles are on an Agile team?
Typically a Product Owner, a Scrum Master or Agile coach, and Developers, meaning everyone who does the work.
Why should Agile teams be small?
Communication channels grow quickly with size: five people have 10 channels, ten have 45. Small teams coordinate faster.
What is an Agile team working agreement?
A short set of rules the team agrees on, such as core hours, communication norms and how decisions are made.
Do Agile teams have a team leader?
Not in the traditional sense. Leadership is shared, with the Product Owner owning priorities and the Scrum Master supporting effectiveness.
What are T-shaped skills in an Agile team?
Deep expertise in one area plus broader skills in others, which lets team members help each other and reduces bottlenecks.
How long should an Agile team stay together?
As long as possible. Stable, long-lived teams learn to work well together and become more predictable. See Agile team structures.