Skip to content
BENIBIX Learn

Scrum Team and Roles

Level 2 Β· Scrum

The three jobs in a Scrum Team: Product Owner, Scrum Master and Developers. What each one is accountable for, and why there is no boss inside.

Course contentsLesson 4 of 19

After this lesson you can

  • Name the three Scrum accountabilities
  • Say what each one is accountable for
  • Explain what self-managing means

12 mincovers 5 glossary entries

Worth reading first: Scrum Framework Basics

Who does what in a Scrum Team

A Scrum Team is the small group that does the work, typically 10 people or fewer. It has one Product Owner, one Scrum Master and the Developers. The guide calls these three accountabilities rather than job titles. There are no sub-teams and no ranks inside the team.

The Product Owner decides what to build next. They keep one ordered list of all the work the product might need, and they are the one person who sets its order. They talk with users, buyers and leaders to learn what matters most. Others can ask, but the call on the order is theirs.

The Developers are everyone who builds the product. Coders count, and so do testers, designers and writers. They plan the sprint's work, decide how to do it and hold each other to the team's standard of finished. Older guides called them the Development Team.

The Scrum Master helps the team use Scrum well. They teach the rules, help the meetings stay useful and clear blocks the team cannot move alone. They also help the wider company work with the team. The guide calls them true leaders who serve the team, not managers who give orders.

The whole team is self-managing. It decides for itself who does what, when and how. Nobody hands out tasks. The team still has a goal and limits, and a person outside it may still set its pay. Inside the team, though, the work is shared out by the people doing it.

Teams bigger than about 10 tend to talk less well and plan more slowly. The guide says to split them into a few smaller Scrum Teams. They work on one product, with one Product Owner and one list between them.

The common mistake is turning the Scrum Master into a boss who hands out tasks. The other is a Product Owner who is really a group of people. One person must own the order of the list. If not, the team gets three answers to every question.

The three accountabilities in a Scrum Team

AccountabilityHow manyAccountable for
Product OwnerOne personWhat to build next, and in what order
Scrum MasterOne personHelping the team and company use Scrum well
DevelopersThe rest of the teamBuilding a usable piece each sprint
Three jobs in one small team. Nobody inside it is the boss of the rest.

Worked example

Lucy stops handing out tasks

Lucy is the new Scrum Master for a team of 8 in Leeds. On day one the Developers wait for her to say who does each task, as their old manager did.

She tells them to pick the work themselves at planning. Within 3 sprints they finish about 20% more, mostly because people take the tasks they know best.

The words for this lesson5

Check yourself

Who decides the order of work for a Scrum Team?

Finished this lesson?

Marking it complete also marks its 5 glossary entries learned, which updates your roadmap and your saved page. 0 are already marked.