Most "Scrum Teams" Aren't Actually Running Scrum—and the Confusion Almost Always Starts With the Roles
When teams say they "do Scrum" but stakeholders still dictate sprint content, or when Scrum Masters are secretly project managers, or when the Product Owner disappears for two weeks at a time—they're not doing Scrum. They're doing something that borrowed Scrum's vocabulary without its structure. The Scrum Guide defines three and only three roles in a Scrum Team, and the way each role is accountable is precise. Here's what each one actually does.
The Three Scrum Roles: An Overview
The 2020 Scrum Guide, the authoritative reference for the Scrum Alliance CSM exam, calls the team structure a "Scrum Team" composed of three accountabilities: Product Owner, Scrum Master, and Developers. The word "accountability" is deliberate—each role owns specific outcomes, not just tasks. A Scrum Team is small, typically 10 or fewer people, self-managing, and cross-functional. There are no sub-teams or hierarchies within a Scrum Team.
What Is the Product Owner Actually Accountable For?
The Product Owner (PO) is accountable for maximizing the value of the product resulting from the work of the Scrum Team. This is accomplished through effective Product Backlog management. Specifically, the PO is accountable for: developing and explicitly communicating the Product Goal, creating and clearly expressing Product Backlog items, ordering the Product Backlog, and ensuring the Backlog is transparent, visible, and understood.
The PO may do the above work themselves or delegate it to others—but they remain accountable for it. This is a critical distinction. A PO can ask a business analyst to write user stories, but the PO is still responsible for whether those stories reflect the right value priorities. Nobody else can override the PO's ordering of the Product Backlog. Not the Scrum Master. Not a manager. Not a stakeholder, even a senior one.
In practice, strong Product Owners are ruthless prioritizers. They understand that a Product Backlog with 400 items is nearly useless; the top 20–30 items should be refined, specific, and value-ordered. They say no frequently—to new feature requests, to scope creep, to "urgent" items that aren't really urgent when weighed against existing priorities. The ability to make hard prioritization decisions with incomplete information is the core skill of an effective PO.
What the PO is NOT: the PO is not the team's manager, not a project manager, and not the person who approves every task before it starts. POs who try to control how Developers do their work undermine self-management and erode team performance.
What Is the Scrum Master Actually Accountable For?
The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide, helping the Scrum Team and organization understand Scrum theory and practice, and the Scrum Team's effectiveness. The Scrum Master is a true leader who serves the Scrum Team and the larger organization. This is why the 2020 Scrum Guide uses the term "accountable for" rather than "responsible for managing"—the Scrum Master doesn't manage the team; they enable it.
The Scrum Master's service to the Scrum Team includes coaching the team in self-management and cross-functionality, helping focus on creating high-value Increments, removing impediments to progress, and ensuring all Scrum events take place and are productive. The Scrum Master's service to the organization includes leading, training, and coaching the organization in Scrum adoption and empirical product development.
A common misconception is that the Scrum Master runs every meeting. The Scrum Master facilitates Scrum events as needed—but a well-functioning Scrum Team often self-facilitates its Daily Scrum without the Scrum Master's direct involvement. The Scrum Master creates conditions where the team can work effectively, then gets out of the way. If a Scrum Master is indispensable to every team discussion, something is wrong with the team's self-management.
Another misconception: the Scrum Master is not a project manager in disguise. Project managers track tasks, manage timelines, and report to stakeholders on progress. Scrum Masters remove impediments, coach on process, and protect the team's focus. If a Scrum Master is updating a Gantt chart, creating status reports for senior leadership, or assigning tasks to Developers, they've drifted out of the Scrum Master role.
What Are Developers Actually Accountable For?
The Scrum Guide uses the term "Developers" to refer to all the people in the Scrum Team who are committed to creating any aspect of a usable Increment each Sprint. This is not limited to software engineers. Designers, testers, data scientists, writers, and other specialists may all be Developers within their Scrum Team.
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, and holding each other accountable as professionals. Nobody assigns work to Developers in Scrum—they pull work from the Sprint Backlog themselves, deciding who does what based on their collective judgment. This self-management is what makes Scrum teams faster and more adaptive than traditionally managed teams.
The Definition of Done is a formal description of the state of the Increment when it meets quality standards. Developers create and own the Definition of Done. If an organization has a Definition of Done, Developers must minimally comply with it. This concept is frequently tested on the CSM exam because it's often misunderstood in practice.
How the Roles Interact: Common Failure Modes to Know for the CSM Exam
The CSM exam tests these role boundaries heavily through scenario questions. Common scenarios include: a manager tries to add work to a Sprint in progress (the Scrum Master protects the Sprint and redirects the manager to the Product Owner); the Product Owner wants to attend the Daily Scrum and give feedback to Developers (the PO can observe but shouldn't direct the Developers' discussion); stakeholders ask the Scrum Master when a specific feature will be delivered (the Scrum Master redirects to the Product Owner and helps educate stakeholders on empirical forecasting).
The pattern the exam rewards is role clarity combined with collaborative problem-solving. The right answer is rarely "refuse and escalate"—it's usually "stay within your role while actively supporting the team and organization."
SimpuTech's CSM AI tutor includes scenario-based questions on role accountabilities, common Scrum anti-patterns, and the Scrum Guide's exact language. Try it free to test your understanding before exam day.
Ready to understand the events these roles participate in? Read Sprint Events and Artifacts: A Visual Guide for CSM Candidates to map out how the framework connects.
Certification details verified against scrumalliance.org as of March 2026. Requirements and fees are subject to change—confirm current details at scrumalliance.org before registering.
Ready to put this into practice?
SimpUTech's Certified Scrum Master (CSM) AI Study Coach gives you personalized practice, instant explanations, and a study plan that adapts to your level.
Start Your Free 3-Day Trial