Agile Roles

What are Agile Roles?

Agile roles are the responsibilities held by people in and around an agile team. Scrum names three, Product Owner, Scrum Master and Developers, and organizations often add coaches, business analysts and stakeholders.

Updated November 2026 · 3 min read


Agile roles are the defined responsibilities within an agile team and the people around it: who decides what to build, who builds it, who helps the team work well and who coordinates across teams. The best-known set comes from Scrum, which names three accountabilities: Product Owner, Scrum Master and Developers. Other frameworks add or rename roles, and most organizations add supporting roles such as agile coaches, business analysts and stakeholders.

Clear roles matter because agile pushes decisions down to teams. If nobody knows who orders the backlog or who removes blockers, those decisions either stall or get made by whoever shouts loudest.

The three core Scrum roles

RoleAccountable forTypical activities
Product OwnerMaximizing the value of the product and ordering the backlogSets the Product Goal, writes and orders backlog items, works with stakeholders, accepts work
Scrum MasterThe team's effectiveness and its use of ScrumCoaches the team, facilitates events when needed, removes impediments, helps the wider organization understand Scrum
DevelopersCreating a usable increment each sprintPlan the sprint, build and test the work, keep to the definition of done, hold each other accountable

"Developers" in the Scrum Guide means everyone doing the work, including designers, testers, analysts and engineers. The 2020 edition dropped the term "Development Team" and talks of one Scrum Team to reduce the sense of separate groups. It says a Scrum Team is typically 10 or fewer people.

Supporting Agile roles

  • Stakeholders. Customers, sponsors, sales, support and others who give input and feedback, especially at sprint reviews.
  • Agile coach. Helps teams and leaders adopt and improve agile practices, often across several teams.
  • Agile business analyst. Helps clarify needs and turn them into well-formed backlog items.
  • Product manager. In organizations that split the roles, owns market strategy and the roadmap while product owners handle team backlogs.
  • Engineering or delivery manager. Supports people's growth, hiring and technical direction without assigning sprint tasks.

Roles in other frameworks

  • Kanban. The Kanban Method does not require any new roles. It describes two optional ones: the Service Request Manager, who orders incoming work, and the Service Delivery Manager, who focuses on flow.
  • Extreme Programming (XP). Uses roles such as customer, programmer, coach and tracker.
  • Scaled frameworks. SAFe adds roles including the Release Train Engineer, Product Management and System Architect to coordinate many teams on an agile release train. LeSS keeps Scrum's roles but has one Product Owner across several teams.

An example

Consider a hypothetical company with eight people building a customer portal: a product manager, two backend engineers, two frontend engineers, a designer, a tester and a project manager who assigns tasks daily. Work is slow because every question goes through the project manager.

The company reorganizes into a single Scrum team. The product manager becomes Product Owner. The project manager, who is good at removing blockers and running meetings, trains as Scrum Master and stops assigning tasks. The engineers, designer and tester become the Developers and plan their own sprint work. Within a few sprints, decisions about how to build things are made in the team in minutes rather than queued for a daily assignment meeting, and the Product Owner spends more time with customers because the Scrum Master handles process questions.

Common pitfalls

  • Renaming without changing. A project manager retitled Scrum Master who still assigns tasks keeps the old system in place.
  • Combining Product Owner and Scrum Master. One person deciding priorities and protecting the team from priority changes faces a conflict of interest.
  • Part-time everything. A Product Owner spread across five teams cannot be available enough to any of them.
  • Ignoring managers. Line managers still exist in most agile organizations. Define what they do, or they will fall back on directing work.

Agile roles shape agile team structure, show up in each of the agile ceremonies and connect to wider questions of team topologies and cross-functional teams.

Frequently asked questions

What are the three roles in a Scrum team?

Scrum names three accountabilities. The Product Owner maximizes product value and orders the backlog. The Scrum Master is accountable for the team's effectiveness and its use of Scrum, coaching and removing impediments. The Developers create a usable increment each sprint, and the term covers everyone doing the work, including designers, testers, analysts and engineers, not only programmers.

Should one person be both Product Owner and Scrum Master?

Combining the Product Owner and Scrum Master roles is generally a mistake. The Product Owner decides priorities, while the Scrum Master helps protect the team's process, including from disruptive priority changes, so one person doing both faces a conflict of interest. Spreading either role too thin, such as one Product Owner across five teams, causes similar problems with availability.

What roles does Kanban define compared with Scrum?

The Kanban Method does not require any new roles. It describes two optional ones: the Service Request Manager, who orders incoming work, and the Service Delivery Manager, who focuses on flow. Scrum, by contrast, defines three required accountabilities: Product Owner, Scrum Master and Developers. Extreme Programming uses its own roles, such as customer, programmer, coach and tracker.