Product Owner¶
The Product Owner is responsible for maximizing the value of the product developed by the team.
Main Responsibilities:¶
- Owns and manages the Product Backlog.
- Clearly communicates the vision and goals of the product.
- Prioritizes work based on business value, customer needs, and stakeholder input.
- Ensures the development team understands what to build and why.
- Collaborates with stakeholders, users, and the team continuously.
Key Traits:¶
- Decisive, accessible, business-savvy.
- Acts as the voice of the customer.
Scrum Master¶
The Scrum Master is the coach, facilitator, and protector of the team. They ensure that Scrum is being applied correctly and help the team improve continuously.
Main Responsibilities:¶
- Helps the team understand and use Scrum principles effectively.
- Removes impediments that block progress.
- Facilitates meetings like Daily Scrums, Sprint Reviews, and Retrospectives.
- Shields the team from outside disruptions.
- Works with the Product Owner to ensure a well-prepared backlog.
Key Traits:¶
- Servant leader, supportive, skilled in facilitation and communication.
- Not a manager or boss, focuses on team empowerment.
Developers (Development Team)¶
The Developers (sometimes called the Development Team) are the people who do the actual work of building the product during the Sprint.
Main Responsibilities:¶
- Deliver a usable, potentially shippable product increment at the end of each Sprint.
- Organize themselves to complete the work.
- Participate in Sprint Planning, Daily Scrum, Reviews, and Retrospectives.
- Maintain high technical quality and follow the Definition of Done.
Key Traits:¶
- Cross-functional (includes all skills needed: coding, testing, design, etc.).
- Self-organizing, collaborative, and committed to the Sprint Goal.
How the roles interact¶
graph TD
ST[Stakeholders] -->|needs and feedback| PO[Product Owner]
PO -->|ordered Product Backlog| DEV[Developers]
DEV -->|Increment| ST
SM[Scrum Master] -.->|coaching, facilitation| PO
SM -.->|removes impediments| DEV
SM -.->|shields from disruption| ORG[Organization]
Solid edges are the value flow, and dotted edges are enabling work. The Scrum Master never sits between the Product Owner and the Developers, which is the difference between coaching and managing.
Summary Table¶
| Role | Focus | Key Responsibilities |
|---|---|---|
| Product Owner | Product value & direction | Backlog management, stakeholder collaboration |
| Scrum Master | Process & team efficiency | Coaching, facilitating, removing blockers |
| Developers | Delivering the product | Building, testing, collaborating on implementation |
Keynotes¶
- There are no sub-teams or hierarchies within the Scrum Team.
- Scrum encourages collaboration and shared responsibility across all roles.
- Everyone on the team works toward the same Sprint Goal.
Anti-patterns¶
| Anti-pattern | Why it breaks Scrum |
|---|---|
| Scrum Master assigns tasks | Destroys self-organization, since the Developers pull their own work. |
| Product Owner is a committee | Ordering the backlog needs a single accountable decision-maker. |
| Product Owner is unavailable | Questions block, and the team guesses at business value. |
| Scrum Master is also the line manager | Team members will not raise problems honestly to someone who writes their review. |
| Developers split into "the testers" and "the coders" | Scrum has no sub-teams, and the whole team owns the Definition of Done. |
Check Your Understanding¶
#
A stakeholder wants a new feature added mid-Sprint. Who decides, and how?
#
Why is the Scrum Master described as a "servant leader" rather than a manager?