Agile Team Roles and Responsibilities
What to Know
Understand accountability boundaries in Scrum and general Agile teams.
Product Owner (PO): maximizes value; owns and orders the Product Backlog; defines and communicates the Product Goal; is one person, not a committee; makes prioritization decisions. The PO may delegate work but remains accountable.
Scrum Master (SM): serves the team and organization; removes impediments; coaches; facilitates events; ensures Scrum is understood and enacted. The SM is a servant-leader, not a boss.
Developers: self-organize; turn backlog items into an Increment; own the Sprint Backlog and the Definition of Done; estimate; decide how to build.
Stakeholders: provide feedback and context; do not direct the team's daily work. In scaled settings, roles like Release Train Engineer or Team Coach exist.
Traps
- "The Scrum Master assigns tasks." No - the team self-organizes.
- "The PO tells developers how to build." No - PO owns what/why, developers own how.
- PO is a committee. The PO must be one person for clear decisions.
- SM as project manager. The SM facilitates and removes impediments, not commands.
- Stakeholders dictating priorities directly to developers bypasses the PO - a process smell.
- Confusing accountability with delegation - the PO can delegate but stays accountable.
Rule of Thumb
Ask what and why → PO. Ask how → Developers. Ask process/enablement → Scrum Master. Ask context/feedback → Stakeholders.
Worked Example
A stakeholder emails a developer demanding a feature next Sprint. The correct flow: the developer routes the request to the PO, who evaluates value and orders the Product Backlog. The SM does not arbitrate priorities; the PO does.