# The Three Accountabilities

Distinguish the Product Owner, Scrum Master, and Developers by what each answers for and by common role violations.

Duration: 11 min

Scrum names accountabilities rather than mandatory job titles. The Product Owner answers for value and backlog order. The Scrum Master answers for effectiveness and the conditions for self-management. Developers collectively build a usable Increment and decide how to organize their work.

The quickest diagnostic is to watch who assigns tasks. In healthy Scrum, Developers pull and manage their own work; neither the Product Owner nor the Scrum Master distributes daily assignments.

## fmap-m2-l2-v1

The local animation draft remains separate from learner delivery. Keep this atom in review until a final provider asset and human-reviewed captions are approved; use the digest as the equivalent text path.

## fmap-m2-l2-digest

### Three accountabilities: is and is not

Scrum names accountabilities—who answers for what—not job titles. Some organizations use plainer labels such as value owner or team coach. This course uses the standard terms because they are the terms learners will meet in job advertisements and workplaces.

**Product Owner.** One person is accountable for maximizing product value, chiefly by owning and ordering the Product Backlog. When stakeholders disagree, this person turns disagreement into a sequence. The Product Owner is not a requirements secretary who records wishes in arrival order, and not a committee whose decisions move at the speed of a room.

**Scrum Master.** This person is accountable for the team's effectiveness. They coach self-management, help remove impediments the team cannot remove, and establish the conditions in which Scrum functions. The Scrum Master is not a boss, project manager, task assigner, or process police officer. The useful modern framing is a leader who serves.

**Developers.** These are all the people who build the Increment—not only software coders. Together they are cross-functional, holding the skills needed to make an item usable. They are self-managing: they decide who does what, when, and how.

In a school fundraising gala, the person who owns the ordered value list plays the Product Owner accountability; the coordinator who clears district paperwork and coaches self-management plays the Scrum Master accountability; and the volunteers who book, call, create, and coordinate are Developers.

The fastest diagnostic is to watch who assigns work. In real Scrum, nobody assigns Developers their daily tasks. They pull and organize the work themselves.

## fmap-m2-l2-i1

Three accountabilities and one violation zone make the boundary visible. If a trap caused hesitation, use its feedback as the lesson rather than treating the activity as a score.