Scrum has exactly three roles. Not four. Not five. Three. This is one of the most intentional design decisions in the framework — because every role that isn't in Scrum (Project Manager, Team Lead, QA Manager) either gets absorbed into one of the three, or it means there's a structural problem in how the team is organized.
Learning Objectives
By the end of this lesson you will be able to:
- Define the responsibilities of the Product Owner, Scrum Master, and Developers
- Explain why Scrum has no "Project Manager" role
- Describe where QA fits in the Scrum team structure
- Articulate the concept of collective ownership of quality
Role 1: The Product Owner — Answering "WHAT?"
The Product Owner (PO) is accountable for maximizing the value of the product. They are the single voice of the business, the stakeholders, and the users inside the Scrum team.
Core responsibilities:
- Creating and maintaining the Product Backlog — the ordered list of everything that needs to be done
- Prioritizing backlog items based on business value, risk, and user needs
- Defining acceptance criteria so the team knows when a story is done
- Being available to answer questions about requirements during the sprint
What the PO is NOT:
- A traditional requirements analyst who writes specs and throws them over a wall
- The person who approves test results (that's a QA responsibility)
- A manager who assigns tasks to developers
For QA: The PO is your primary source of truth on "what should the system do?" When you find a bug and aren't sure if it's actually a bug (maybe it's intentional behavior), the PO or the acceptance criteria they defined is where you look first.
Role 2: The Scrum Master — Answering "HOW?"
The Scrum Master is accountable for the team's effectiveness. They ensure the Scrum framework is understood and enacted, and they remove the impediments that slow the team down.
Core responsibilities:
- Facilitating Scrum ceremonies (but not running them as a chairman — guiding them as a servant)
- Removing blockers: if a developer is waiting two days for an environment to be set up, the Scrum Master fixes that
- Protecting the team from external interference during a sprint
- Coaching the team on Agile practices and Scrum theory
What the Scrum Master is NOT:
- A project manager with a Gantt chart
- A boss who decides who works on what
- A secretary who runs status meetings
The servant-leader model: The Scrum Master serves the team, not the organization. Their job is to make the team more effective — even if that means pushing back on management demands.
Role 3: Developers — Answering "HOW DO WE BUILD IT?"
"Developers" in Scrum doesn't mean "people who write code." It means anyone who does the work needed to create the Increment in a sprint. This explicitly includes:
- Software engineers (backend, frontend, mobile)
- QA engineers / testers
- UX/UI designers
- DevOps / platform engineers
Core responsibilities:
- Creating a plan for the sprint (the Sprint Backlog)
- Instilling quality by adhering to the Definition of Done
- Adapting the plan each day during the Daily Scrum
- Holding each other accountable for meeting the Sprint Goal
The key implication: There is no "QA Department" separate from "the team" in Scrum. Quality is a collective responsibility of all Developers — not something that gets handed off at the end.
Where Does QA Fit?
In Scrum, a QA engineer is a Developer. Full stop.
This means:
- You are present from Sprint Planning, not just from the testing phase
- You help define acceptance criteria alongside the PO
- You provide test estimates as part of the sprint commitment
- You are one voice in the collective decision: "Is this story done?"
- Your perspective — "Is this actually going to work for the user?" — is as valid as a developer's opinion on architecture
The teams that struggle with quality in Scrum are usually the ones where QA is still structured as an external gate rather than an internal team member.
Why There's No Project Manager
The PM's traditional tasks get distributed across the three Scrum roles:
| PM task | Scrum equivalent |
|---|---|
| Define scope | Product Owner (backlog) |
| Prioritize work | Product Owner |
| Remove blockers | Scrum Master |
| Protect team from distractions | Scrum Master |
| Track progress | The whole team (Sprint Backlog, burndown) |
| Report status upward | Scrum Master + PO |
This isn't about eliminating people — it's about distributing accountability instead of concentrating it in one role that becomes a bottleneck.
Pro Tips
If your team has a "QA Lead" who approves all bugs before they go to the developer, that's a Waterfall quality gate wearing a Scrum costume. In a healthy Scrum team, any QA engineer can raise, own, and close a defect.
The most common misuse of the Scrum Master role: turning them into a project manager who tracks tasks, creates Jira boards, and updates stakeholders. That's not a Scrum Master — that's a project coordinator with a different title.
Summary
- Scrum has exactly three roles: Product Owner (WHAT), Scrum Master (HOW the team works), and Developers (HOW it gets built).
- The Product Owner owns the backlog and is accountable for product value.
- The Scrum Master is a servant-leader: they facilitate, remove impediments, and protect the team.
- "Developers" includes QA engineers — quality is a shared, collective responsibility.
- There is no separate QA department in Scrum; testing is a team activity integrated into every sprint.