Skip to content

Scrum Team Accountabilities

Step 3 of 18

Scrum Team Accountabilities: Developers, Product Owner, and Scrum Master

Introduction

Scrum Team accountabilities tell you who makes each decision. If a stakeholder asks for a feature halfway through the Sprint, the Product Owner considers its value and place in the Product Backlog. The Developers assess what the change would mean for their plan. The Scrum Master helps people work together without taking those decisions away from them.

This PSM I lesson covers the Scrum Team in Scrum.org’s Understanding and Applying the Scrum Framework focus area. You will practice assigning decisions to the right accountability, distinguish delegation from accountability, and learn what several teams working on one product share.

Learning objectives

  • Describe the Scrum Team: size, cross-functionality and the single focus on the Product Goal.
  • Define the accountabilities of the Developers, the Product Owner and the Scrum Master.
  • Explain the services the Scrum Master provides to the Scrum Team, the Product Owner and the organization.
  • Decide who owns a decision in a given scenario.
  • Explain how several Scrum Teams working on one product share the Product Backlog, Product Owner and Definition of Done.

1. The Scrum Team

A Scrum Team includes a Scrum Master, a Product Owner, and Developers working toward one Product Goal. It has no internal hierarchy or separate delivery sub-teams. It brings together the skills to create value and decides how to organize its work. See how self-managing Scrum Teams make decisions for what this means when several specialists need to coordinate.

The Scrum Guide describes a typical team as 10 or fewer people in total, including the Product Owner and Scrum Master. If growth makes coordination difficult, consider splitting into cohesive teams focused on the same product. The entire Scrum Team is accountable for a valuable, usable Increment each Sprint. Its work can include discovery, collaboration with stakeholders, testing, delivery, and operation.

Aspect What the guide says Common misreading
Size Typically 10 or fewer in the whole Scrum Team Treating 10 as a mandatory maximum
Structure One team, no sub-teams "Test team" and "development team" as separate sub-teams
Skills Cross-functional Handing off to an outside QA or operations group every Sprint
Decisions Self-managing A manager assigns tasks to Developers
Accountability The Scrum Team for a valuable, usable Increment Treating quality as a separate department’s responsibility after the Sprint

Exam tip. In the 2020 guide there is no "Development Team" inside the Scrum Team. The term is Developers, and the Scrum Team consists of the Scrum Master, the Product Owner and the Developers. If an option mentions a sub-team called the Development Team, treat it with suspicion.

2. Developers

Developers contribute to a usable Increment. The term can include testers, designers, analysts, and other specialists as well as programmers. Their accountabilities cover four decisions in everyday work:

  • Make the Sprint Backlog visible so the team can inspect its plan.
  • Meet the Definition of Done as part of delivering the work.
  • Update the plan daily as progress toward the Sprint Goal becomes clearer.
  • Hold one another to professional standards.

Developers can share or specialize in tasks as they see fit. Their planning and quality accountabilities apply to the group, including when a task spans more than one specialty.

Example: who decides how much to take into the Sprint?

At Sprint Planning, the Product Owner proposes how the product could increase its value in the Sprint and asks the Developers to forecast 14 Product Backlog items. The Developers believe that, given their capacity and the Definition of Done, they can finish only 9, but that these 9 will fulfil the proposed Sprint Goal. The Developers select the items in discussion with the Product Owner. The whole Scrum Team agrees on the Sprint Goal and is accountable for the Increment. The Product Owner may influence by clarifying and by re-ordering, but cannot dictate the amount of work.

3. The Product Owner

The Product Owner is accountable for the value the product delivers and for managing the Product Backlog effectively. That means communicating the Product Goal, making items clear, deciding their order, and keeping the backlog visible and understood.

One person holds the accountability. That person can ask others to draft items or help gather evidence, and still answers for the backlog and its ordering. Stakeholders can propose changes and explain their value. The Product Owner weighs their input against the Product Goal.

Example: a Product Owner under pressure

A telecommunications company launches a self-service portal. The sales director, the call-centre manager and the legal department each send the Scrum Team a list of "top priority" features. The Product Owner does not forward the lists to the Developers and does not let three people prioritise. Instead, the Product Owner collects the requests, estimates the value of each against the Product Goal ("reduce support calls by 30% in six months"), orders the Product Backlog accordingly, and explains the ordering transparently at the Sprint Review. The sales director accepts that the call-centre feature goes first. This is the Product Owner doing the job: maximizing value, one voice, transparent ordering.

4. The Scrum Master

The Scrum Master helps the team and the organization apply Scrum and is accountable for improving the Scrum Team’s effectiveness within the framework.

Services to the Scrum Team

Help people coordinate their own work, develop the skills needed to deliver, and address impediments. The Scrum Master also ensures that the five Scrum events happen, serve their purpose, and stay within their timeboxes. For example, if a test environment requires two weeks of approvals, the Scrum Master can bring the team and the platform group together to unblock access.

Services to the Product Owner

Help the Product Owner communicate the Product Goal, clarify backlog items, plan using evidence, and collaborate with stakeholders. For example, the Scrum Master can facilitate a session where support and sales compare customer feedback before the Product Owner reorders work.

Services to the organization

Coach people adopting Scrum and help resolve obstacles between teams and stakeholders. If a sponsor asks for fixed scope several months ahead, the Scrum Master can explain what the team already knows and when inspection will provide a better forecast.

Comparison: Scrum Master versus related jobs

Job Typical focus Scrum Master difference
Project manager Plans, assigns tasks, tracks scope, budget and schedule Scrum Master does not assign work or report progress on behalf of the team; Developers self-manage
Team lead Decides how the work is done and by whom Scrum Master coaches, does not decide for the team
Scrum administrator / secretary Schedules meetings, takes minutes Scrum Master ensures events happen and are effective, but does not do clerical work for the team
Product Owner Value and Product Backlog Scrum Master does not order the Product Backlog or decide priorities
Agile coach (external) Advises across teams Scrum Master is a member of the Scrum Team and accountable for its effectiveness

Example: a Scrum Master serving rather than managing

During Sprint Planning, the Developers are unsure how to estimate a new type of work, and the Product Owner wants a date commitment. The Scrum Master does not give the estimate and does not promise a date. The Scrum Master facilitates a conversation: reminding everyone that the Sprint Goal is the commitment, suggesting a small spike to reduce uncertainty, and coaching the Product Owner on forecasting with evidence (covered in a later lesson). The team makes the decisions; the Scrum Master improves the conditions in which they decide.

5. Worked example: who owns the decision?

Scenario. Halfway through a Sprint, a major customer asks for a new report. The account manager tells a Developer directly: "Please add this report, it only takes a day." The Developer is concerned because the Sprint Goal is "Reduce checkout abandonment". What happens next?

Step 1: Identify accountabilities. The Product Owner is accountable for the Product Backlog and its ordering. The Developers create and adapt the Sprint Backlog and commit to the Sprint Goal. The Scrum Master is accountable for helping the team and organisation understand Scrum.

Step 2: Route the request. The Developer should refer the account manager to the Product Owner. The account manager can try to convince the Product Owner that the report adds value.

Step 3: Evaluate. If the Product Owner agrees that it is valuable, the item is added to the Product Backlog and ordered. If it is more urgent than the Sprint Goal, the Product Owner, not the account manager, may consider whether the Sprint Goal is obsolete (only then is cancelling the Sprint an option). If the Sprint Goal remains valid, the Developers and Product Owner can discuss whether to change the selected scope without endangering that goal. Otherwise, leave the request in the Product Backlog for future selection.

Step 4: Scrum Master's role. The Scrum Master helps the account manager understand why requests go through the Product Owner (to keep one ordered Product Backlog) and works with the organisation so that direct interruptions decrease.

Why the alternatives are weaker. The Developer silently doing the extra work hides a change in the Sprint Backlog and may endanger the Sprint Goal. The Scrum Master accepting or refusing the request would breach the Product Owner's accountability. The Product Owner telling the Developers to "just fit it in" ignores their ownership of the Sprint Backlog.

6. Several Scrum Teams on one product

Larger products may need more than one Scrum Team. The guide notes that, when multiple Scrum Teams work on the same product, they should share the same Product Goal, Product Backlog and Product Owner. All teams must jointly define and follow the same Definition of Done, respecting any organizational minimum, so that the combined work forms one integrated Increment. (The guide describes the Definition of Done in the artifacts section.) Practical consequences:

  • There is a single Product Backlog, ordered by one Product Owner, not one per team.
  • Each team has its own Sprint Backlog and Developers; each team plans and decides how to meet the Sprint Goal.
  • The Increment must be integrated and usable, which makes a shared Definition of Done important.
  • Teams may synchronise their work but should not create new hierarchical roles.

Example

An e-commerce company runs three Scrum Teams on one marketplace product. They share the Product Owner and a single Product Backlog. Team A works on search, Team B on checkout and Team C on seller tools. The three teams hold their own Sprint Plannings but refine the Product Backlog together, and each team's Increment must meet the common Definition of Done, including automated integration tests. For example, if the checkout team verifies transactions against a new tax API but the seller tools team still uses the old response format, both teams should investigate the integration before counting the changes as part of the same usable product. The shared Definition of Done makes clear that team-level tests are only one part of that decision.

7. Common pitfalls and exam tips

  • The Product Owner is one person. A committee or a "Product Owner team" is not allowed, although the Product Owner may delegate tasks and take advice.
  • Accountability versus responsibility. The Product Owner can delegate the writing of Product Backlog items; they remain accountable.
  • Scrum Master is not the boss. The Scrum Master does not decide what the Developers build, how they build it or who does what. They serve, coach and facilitate.
  • The Scrum Master is not the only person who can facilitate. The Scrum Master ensures events happen and are productive; any member may facilitate when appropriate.
  • Specialties and hierarchy are separate. A tester or architect can be a Developer. Their job titles do not give them decision authority over other Developers within the team.
  • Product focus. Scrum Teams organize around a product and its Product Goal. The guide gives no rule that a particular team must remain together for the product’s lifetime.
  • Size. A Scrum Team typically has 10 or fewer people. Consider whether splitting a larger team would make communication and delivery easier while preserving one product focus.
  • Stakeholders are not part of the Scrum Team. They collaborate, mostly at the Sprint Review and through the Product Owner.

Exam tip. In "who should…" questions, match the verb to the accountability: order the Product Backlog is the Product Owner; create the Sprint Backlog and adhere to the Definition of Done is the Developers; establish Scrum and remove impediments is the Scrum Master.

8. Mini case study

Context. Helio Energy builds a mobile app for monitoring home solar panels. The Scrum Team has 5 Developers, a Product Owner and a Scrum Master. Recent events: (1) the head of engineering asks the Scrum Master for a weekly status report listing each Developer's progress and expects the Scrum Master to reassign tasks if somebody is late; (2) the Product Owner has told the team that she is too busy and that the marketing, sales and support leads will "vote" on the order of the Product Backlog; (3) the Developers say that quality assurance is carried out by another department after the Sprint.

Question. Which Scrum accountabilities are being misunderstood, and what should the Scrum Master do?

Commented solution.

  1. The Scrum Master as a manager. The Scrum Master is accountable for the Scrum Team’s effectiveness. Developers organize their work and hold one another accountable. The Scrum Master should explain that the Developers hold each other accountable and that the Sprint Review and the Sprint Backlog provide transparency. If the head of engineering needs information, the team can present the Increment and the Sprint Goal progress.
  2. The Product Owner as a committee. The Product Owner may consult stakeholders, but ordering is her accountability. The Scrum Master helps the Product Owner find techniques for Product Backlog management and facilitate stakeholder collaboration, and may help her delegate tasks (such as writing items) while she keeps accountability.
  3. Outside QA. The Scrum Team should be cross-functional and have all the skills to create a usable Increment. The Scrum Master coaches the team in cross-functionality and, because the organisational structure is the barrier, works with the organisation to remove this impediment, for example by embedding testers in the Scrum Team and including testing in the Definition of Done.

Key terms

  • Accountability: a set of responsibilities that someone answers for; Scrum uses it instead of "role".
  • Scrum Team: one Scrum Master, one Product Owner and Developers; no sub-teams.
  • Developers: people on the Scrum Team who contribute to creating a usable Increment.
  • Product Owner: accountable for maximizing the value of the product and for Product Backlog management.
  • Scrum Master: accountable for establishing Scrum and for the Scrum Team's effectiveness.
  • Product Goal: the long-term objective for the Scrum Team.
  • Impediment: anything that blocks the Scrum Team's progress.
  • Self-managing: the team decides who does what, when and how.
  • Cross-functional: the team has all the skills needed to create value each Sprint.

Summary checklist

  • I know why a Scrum Team typically has 10 or fewer people and works as one unit.
  • I can list the Developers' four accountabilities.
  • I know the Product Owner is one person who may delegate tasks but stays accountable.
  • I can list the Scrum Master's services to the team, the Product Owner and the organization.
  • I can explain why the Scrum Master is not a project manager.
  • I know that multiple teams share one Product Goal, Product Backlog and Product Owner, and a common Definition of Done.
  • I can route a request or decision to the correct accountability.

Sources