The Three Pillars of a Scrum Team
Scrum is intentionally lightweight, but it comes with a defined set of accountabilities. Every Scrum team is made up of exactly three roles: the Product Owner, the Scrum Master, and the Developers (collectively called the Development Team). Understanding who does what — and why — is the foundation of running effective Scrum.
The Product Owner
The Product Owner (PO) is accountable for maximizing the value of the product. Their primary tool is the Product Backlog — an ordered list of everything that needs to be done to improve the product.
Key responsibilities:
- Defining and clearly expressing Product Backlog items
- Ordering backlog items to achieve goals and deliver value
- Ensuring the backlog is visible, transparent, and understood
- Acting as the single voice of the customer and stakeholders
- Accepting or rejecting completed work at the end of each Sprint
The PO is one person, not a committee. They may take input from many stakeholders, but the final prioritization decisions rest with them. When developers have questions about what to build, the PO is the source of truth.
The Scrum Master
The Scrum Master is a servant-leader responsible for the effectiveness of the Scrum Team. They don't manage the team — they enable the team to do its best work by removing obstacles, coaching on Scrum practices, and protecting the team from outside distractions.
Key responsibilities:
- Coaching the team and organization on Scrum theory and practice
- Facilitating Scrum events (Daily Scrum, Sprint Planning, Retrospective, etc.)
- Removing impediments that slow the team down
- Helping the Product Owner with backlog management techniques
- Shielding the team from organizational noise and scope creep
A common misconception is that the Scrum Master is a project manager. They are not. They hold no authority over team members and do not assign tasks. Think of them as a coach and process guardian combined.
The Developers (Development Team)
The Developers are the people who do the actual work of creating a usable increment each Sprint. In the 2020 Scrum Guide update, "Development Team" was simplified to just "Developers," though this includes all skill sets needed — engineers, designers, testers, and anyone else who contributes to the increment.
Key characteristics:
- Cross-functional: The team collectively has all the skills needed to deliver a "Done" increment
- Self-managing: They decide how to accomplish the work, not who tells them what to do
- Accountable as a unit: No sub-teams or individual hierarchies within the Developers
- Optimal size: Typically 3–9 people (small enough to be agile, large enough to be cross-functional)
How the Roles Work Together
| Role | Primary Focus | Key Artifact Owned |
|---|---|---|
| Product Owner | What to build and in what order | Product Backlog |
| Scrum Master | How the team works and improves | Sprint Retrospective outcomes |
| Developers | How to build the increment | Sprint Backlog & Increment |
Common Pitfalls to Avoid
- The "technical PO": A developer who moonlights as PO rarely has the customer focus the role requires.
- The "managing Scrum Master": When a SM starts assigning tasks, the team loses autonomy and trust erodes.
- The siloed developer: If individual developers only work in their specialty and refuse to help elsewhere, the team stops being cross-functional.
When these three roles operate as designed, Scrum becomes a powerful engine for delivering value incrementally. The magic isn't in the process — it's in the accountability and collaboration between these three accountabilities.