Agile guide · Agile roles and teams
Agile Team Structures: Types, Roles and How to Choose One
An Agile team structure is the way people, skills and responsibilities are organised so that a small, cross-functional team can deliver value end to end. Common structures include feature teams, component teams, generalist and specialist mixes, and platform teams, often grouped into larger units as organisations scale.
Key takeaways
- Agile teams are small, cross-functional, self-managing and long-lived.
- Feature teams reduce hand-offs; component and platform teams provide depth and shared services.
- Design structures around the flow of value and minimise dependencies.
- Review structures periodically, but keep teams stable.
What makes a team Agile
- Cross-functional: the team has all the skills needed to turn a backlog item into a finished result.
- Small and stable: typically around ten people or fewer; the 2020 Scrum Guide says a Scrum Team is typically 10 or fewer.
- Self-managing: the team decides how to do its work.
- Long-lived: teams stay together across many projects so that they learn and improve.
- Focused on one goal or product at a time.
See what is an Agile team for the basics.
Common Agile team structures
| Structure | How it works | Strengths | Watch out for |
|---|---|---|---|
| Feature team | Owns complete customer features across all layers | Fast end-to-end delivery, fewer hand-offs | Needs broad skills; shared code needs good practices |
| Component team | Owns one part of the system, such as payments or search | Deep expertise, consistent architecture | Features need several teams; more dependencies |
| Generalist team | Members can work across many types of task | Flexible, avoids bottlenecks | May lack deep expertise |
| Specialist team | Members each hold a distinct skill | High quality in each discipline | Bottlenecks when one skill is overloaded |
| Hybrid (T-shaped) team | Members have one deep skill and broader secondary skills | Balances depth and flexibility | Takes time and support to build |
| Platform team | Provides shared tools and services to other teams | Reduces duplicated effort | Must treat other teams as customers |
Roles in an Agile team
| Role | Focus |
|---|---|
| Product owner | Maximises value; owns and orders the backlog; see Scrum Product Owner |
| Scrum Master or Agile coach | Team effectiveness and removing impediments; see Scrum Master role |
| Developers or team members | Build, test and deliver the work; may include engineers, designers, analysts, testers and writers |
| Stakeholders | Provide input and feedback, especially at reviews |
| Agile project manager (in some organisations) | Coordination across teams, budgets and reporting; see Agile project manager |
How to design your team structure
- Start from the value stream: map how work flows from request to customer; see value stream mapping.
- Choose the team type: prefer feature teams aligned to customer journeys or products, and add component or platform teams only where expertise or scale demands it.
- Size the teams: aim for around five to nine members, and split larger groups.
- Fill skill gaps: list the skills needed to finish work without hand-offs, then hire, train or pair to cover gaps.
- Minimise dependencies: if a team regularly waits on another, adjust boundaries.
- Define how teams coordinate: use practices such as a Scrum of Scrums or shared planning.
- Review regularly: check flow, dependencies and morale every few months and adapt.
Example: from component to feature teams
An online retailer has four component teams (web front end, mobile, checkout services and database) of six people each. A typical feature needs all four, so items wait in queues and a simple change takes six weeks. The company re-forms into three feature teams aligned to customer journeys (browse, buy, account), each with front-end, mobile, back-end and testing skills, plus one small platform team of six for shared infrastructure. With fewer hand-offs, most features are now completed by a single team within one or two sprints.
Structures at scale
- Team of teams: several teams working on one product share a backlog and coordinate; see Large-Scale Scrum (LeSS).
- Agile Release Train: in SAFe, typically 5–12 teams plan and deliver together; see Agile Release Train.
- Squads, tribes, chapters and guilds: a model popularised by Spotify; see squads, tribes, chapters and guilds.
Free templates for this topic
Frequently asked questions
What is the best Agile team structure?
There is no single best structure. Feature teams suit most product work, with platform or component teams where specialist depth or shared services are needed.
How big should an Agile team structure be?
Small, typically around ten people or fewer. Larger groups should usually split into several teams.
What is a cross-functional Agile team structure?
A team that has all the skills needed to deliver a finished result without relying on other teams.
Which Agile team structure is better: feature teams or component teams?
A feature team delivers complete customer features across the system; a component team owns one part of the system.
What is a T-shaped team member in an Agile team structure?
Someone with deep expertise in one area and working knowledge of several others, which helps the team share work.
Does an Agile team structure need a project manager?
Not within Scrum, which has no project manager role. Some organisations keep project managers for cross-team coordination; see Agile project manager.
Who leads in an Agile team structure?
Agile teams are self-managing. The product owner sets priorities, the Scrum Master supports effectiveness, and the team decides how to do the work.
What is a platform team in an Agile team structure?
A team that builds and runs shared tools or services so that other teams can deliver faster.
Should an Agile team structure be co-located?
Co-location helps communication, but many teams work well remotely or in hybrid setups with good tools and agreed working hours.
How often should an Agile team structure change?
Teams benefit from stability, so avoid frequent reshuffles. Review structures every few months and change them when dependencies or goals shift.
How does an Agile team structure coordinate multiple teams?
Through shared backlogs, joint planning, regular cross-team meetings and scaling frameworks; see scaled Agile framework.