Skip to content
Tutorials Center
My learning

Topics

Lesson 6 of 29 ยท The Scrum Framework

Scrum Roles

Learn the Scrum accountabilities: Product Owner, Scrum Master and Developers, how stakeholders fit in, and the role confusions that cause trouble.

Scrum keeps the people structure deliberately simple. The Scrum Guide describes one small Scrum Team with three accountabilities: the Product Owner, the Scrum Master and the Developers. There are no sub-teams, no team leader and no testers-versus-programmers split inside the team. Everyone on the team shares the responsibility for delivering value every Sprint.

The word accountability is chosen on purpose. An accountable person answers for an outcome, but they can share or delegate the work. The Product Owner, for instance, is accountable for the Product Backlog, though others may help maintain it. This lesson explains what each accountability covers, how stakeholders and managers fit around the team, and the confusions that cause the most pain in practice. Start with Scrum at a Glance if you want the big picture first.

One team, three accountabilities

Product Owner Maximizes the value of the product.
Scrum Master Helps the team and organization use Scrum well.
Developers Build a usable Increment each Sprint.

Usually ten people or fewer, with no hierarchy inside.

1 / 2

The Product Owner

The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. How that is done varies widely between organizations, teams and individuals. Concretely, the Product Owner is accountable for:

  • Developing and explicitly communicating the Product Goal.
  • Creating and clearly communicating Product Backlog items.
  • Ordering Product Backlog items so the most valuable work comes first.
  • Ensuring the Product Backlog is transparent, visible and understood.

The Product Owner is one person, not a committee. A committee may be represented by that person, but when the team needs a decision about priorities, there is one voice. For the Product Owner to succeed, the organization must respect their decisions, which show up in the content and ordering of the Product Backlog. Nobody should push the Developers to work from a different set of priorities.

A good Product Owner is available to the Developers every day, understands users and the market, says "no" to low-value requests, and balances the needs of many stakeholders. They do not need to be a technical expert, but they should be able to describe a problem clearly.

The Developers

Developers are the people in the Scrum Team who are committed to creating any aspect of a usable Increment each Sprint. The guide does not specify their skills: those depend on the domain. In a web product they might be programmers, designers, testers, database specialists and writers.

Developers are accountable for:

  • Creating a plan for the Sprint, the Sprint Backlog.
  • Instilling quality by adhering to a Definition of Done.
  • Adapting their plan each day toward the Sprint Goal.
  • Holding each other accountable as professionals.

The team is cross-functional, which means that together the Developers have all the skills needed to turn a backlog item into a working Increment, without waiting for another department. It is self-managing, which means the Developers decide internally who does what, when and how. No one outside the team (not even the Scrum Master or Product Owner) tells the Developers how to turn backlog items into an Increment.

"Developers" does not mean "programmers". In Scrum, a tester is a Developer, and so is a designer. Scrum has no separate "tester" role or "QA team" inside the Scrum Team.

The Scrum Master

The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide, and for the Scrum Team's effectiveness. They are a true leader who serves the team and the wider organization. The title "master" refers to mastery of the framework, not command over people.

The service goes in three directions:

  • To the team: coach the members to manage themselves and cover all the skills they need, keep attention on small high-value Increments that meet the Definition of Done, clear away obstacles, and make sure the events happen, stay useful and stay inside their time-boxes.
  • To the Product Owner: share techniques for stating a Product Goal and keeping the backlog healthy, help the team see why clear backlog items matter, support evidence-based planning, and bring stakeholders into the conversation when asked.
  • To the organization: lead and coach the adoption of Scrum, advise on how to introduce it, explain empirical product development to the people around the team, and take down barriers between stakeholders and the team.

A Scrum Master is not a project manager, not the team's secretary and not the person who assigns work. Often the best sign of a good one is that the team needs them less each month.

Stakeholders

A stakeholder is anyone outside the Scrum Team with an interest in the product: users, customers, executives, support staff, legal. Stakeholders are not an accountability in Scrum, but they matter. They give input at the Sprint Review, inform priorities through the Product Owner and are the reason the team exists. The Product Owner represents the stakeholders' needs on the team; stakeholders do not give orders to the Developers directly.

Managers are usually not part of the Scrum Team either, but they have important work: creating an environment where the team can succeed, removing organizational barriers, and respecting the team's self-management.

Accountabilities at a glance

Who is accountable for what? The matrix below is a stand-in that stores a short list of responsibilities and the accountability that owns each. The owner is the accountable one; some items are shared with helps. It also contains a lookup so you can check a decision, such as "who orders the Product Backlog?". It follows the accountabilities described in the Scrum Guide, in shortened form.

JS Accountability matrix

Press Run (or Ctrl + Enter) to see the console output here.

No output.

No one is accountable for everything: the Product Owner does not decide how the work gets done, and the Developers do not decide what the highest priority is. The boundaries create a healthy tension that keeps value and quality both visible.

Common role confusions

These patterns appear in many organizations, and each one weakens Scrum.

  • The Scrum Master as project manager. The Scrum Master does not assign tasks, track hours or report status upward. If the team waits for the Scrum Master to tell them what to do, it is not self-managing.
  • The Product Owner as a messenger. A Product Owner who only forwards requirements from others, without the authority to decide, becomes a bottleneck. The team needs real decisions.
  • A committee Product Owner. Several people each shouting priorities leaves the Developers unsure what comes first.
  • Developers as "coders only". If testers sit in a separate team and receive work after the Sprint, the Increment is not done inside the Sprint.
  • A team lead who assigns work. Assigning tasks removes the self-management that gives Scrum its energy.
  • Shared Scrum Master and Product Owner in one person. This can be done in tiny teams but mixes the two goals: maximizing value and protecting the process. Watch for neglected coaching.
  • Part-time everything. A person spread across five teams cannot be available, and conversations queue up.

The second model catches some of these. It checks a team description against simple rules: one Product Owner, at least one Developer, a team size of ten or fewer and no extra management role inside the team. Real teams need judgment, so treat it as a checklist for a conversation.

JS Role sanity checker

Press Run (or Ctrl + Enter) to see the console output here.

No output.

If you are about to join a Scrum team, ask two questions: "Who decides the order of the backlog?" and "Who decides how the work gets done?" The answers (one Product Owner, and the Developers themselves) say a lot about how well Scrum is practiced there.

Check your understanding

Quick check ยท 5 questions

of 5 answered You scored / 5 ยท perfect!

  1. 1. Who is accountable for ordering the Product Backlog?

    The Product Owner is accountable for ordering Product Backlog items. They can take input from stakeholders and Developers, but one person answers for the order.
  2. 2. Which statement about Developers in Scrum is correct?

    Developers are everyone doing the work of creating a usable Increment. They manage themselves and decide how to do the work.
  3. 3. What best describes the Scrum Master?

    The Scrum Master is accountable for establishing Scrum and for the team's effectiveness, by coaching, removing impediments and facilitating events.
  4. 4. How should stakeholders influence the work?

    Stakeholders matter, but their needs reach the team through the Product Owner and their feedback at the Review, not by giving orders to the Developers.
  5. 5. Which is a role confusion that weakens Scrum?

    A team lead assigning tasks removes self-management. The other options describe healthy Scrum practice.

Summary

  • A Scrum Team has three accountabilities: Product Owner, Scrum Master and Developers; typically ten people or fewer, with no sub-teams.
  • The Product Owner is one person accountable for the Product Goal, the Product Backlog and its order.
  • Developers are everyone who creates the Increment; they are cross-functional and self-managing.
  • The Scrum Master is a servant leader who coaches the team, helps the Product Owner and the organization, and removes impediments.
  • Stakeholders influence through the Product Owner and the Sprint Review; managers create the environment.
  • Typical confusions are the Scrum Master as project manager, a messenger or committee Product Owner, and a team lead assigning tasks.

Next, see when these people meet in Scrum Events.