Scrum Master exams test the Scrum Guide closely, and many people lose points on things they "learned" from their workplace rather than from the Guide itself. Here are twelve facts from the 2020 Scrum Guide that candidates often get wrong.

1. Scrum has accountabilities

The 2020 Guide describes three accountabilities within the Scrum Team: the Developers, the Product Owner and the Scrum Master. There are no sub-teams or hierarchies.

2. The team is "self-managing"

The 2020 Guide uses self-managing: the Scrum Team internally decides who does what, when and how.

3. A Scrum Team is typically 10 or fewer people

Smaller teams communicate better and are more productive. If a team grows too large, the Guide suggests reorganising into multiple cohesive Scrum Teams focused on the same product, sharing the same Product Goal, Product Backlog and Product Owner.

4. The Product Owner is one person

The Product Owner is one person, not a committee. They may represent many stakeholders, but those wanting a change to the Product Backlog do so by convincing the Product Owner.

5. Each artifact has a commitment

  • Product Backlog → Product Goal
  • Sprint Backlog → Sprint Goal
  • Increment → Definition of Done

6. Sprint Planning answers three topics

Why is this Sprint valuable? What can be Done this Sprint? How will the chosen work get done? The whole Scrum Team crafts the Sprint Goal.

7. The Daily Scrum belongs to the Developers

It's a 15-minute event for the Developers. The Scrum Master ensures it takes place but doesn't have to attend. If the Product Owner or Scrum Master are actively working on Sprint Backlog items, they take part as Developers. The Developers can use any structure they like — the "three questions" are not required.

8. The Sprint Review is a working session

The Scrum Team and stakeholders review what was accomplished and what has changed in the environment, and decide what to do next. The Guide says it should not be limited to a presentation.

9. You don't wait for the Sprint Review to release

Multiple Increments may be created within a Sprint, and an Increment may be delivered to stakeholders before the end of the Sprint. The Sprint Review should never be considered a gate to releasing value.

10. Only the Product Owner can cancel a Sprint

A Sprint could be cancelled if the Sprint Goal becomes obsolete, and only the Product Owner has the authority to cancel it.

11. Work that isn't Done can't be presented

If a Product Backlog item does not meet the Definition of Done, it cannot be released or even presented at the Sprint Review. It goes back to the Product Backlog for future consideration.

12. The Definition of Done can come from the organisation

If the organisation has a Definition of Done standard, all Scrum Teams must follow it as a minimum. If not, the Scrum Team must create one. Several Scrum Teams working on the same product must mutually define and comply with the same Definition of Done.

Test yourself

How many did you already know? Check your understanding with the free Scrum Master practice questions and the free 80-question Scrum Master mock exam, or read the free Scrum Master chapters.

Independent study material based on the Scrum Guide 2020 by Ken Schwaber and Jeff Sutherland (CC BY-SA 4.0). Not affiliated with or endorsed by Scrum.org or Scrum Alliance.