1.Why Scrum Guide Primer is worth getting right
The primer walks through the empirical foundation first, then moves to accountabilities rather than roles, because the 2020 Scrum Guide made that distinction deliberately. A Scrum Master, Product Owner, and set of Developers are not job titles with separate lanes. They are three accountabilities inside one team, and the Guide is explicit that there are no sub-teams or hierarchies. If you have ever seen a Scrum Master act like a project manager assigning tasks, or a Product Owner treated as an outsider who drops requirements over a wall, this lesson explains exactly which rule that breaks.
2.How it works in practice
From there the module pairs each event and artifact with the commitment behind it: the Sprint Backlog exists to serve the Sprint Goal, the Product Backlog exists to serve the Product Goal, and the Increment exists to serve the Definition of Done. This pairing is the fastest diagnostic for a struggling team. If a Daily Scrum feels pointless, the team has usually lost sight of the Sprint Goal it is meant to inspect progress against. If Refinement feels like busywork, the Product Goal is probably too vague to order against. Reading events in isolation, without the commitment they protect, is why so many teams end up running Scrum theatre: same ceremonies, none of the adaptation.
Module 0 does not carry a certificate, and that is intentional. It exists to make sure the knowledge check you take at the end of Foundations, and every simulation after that, rests on the actual 2020 Scrum Guide rather than on secondhand folklore about story points, velocity targets, or command-and-control Scrum Masters. Once you can explain why each event exists and which commitment it protects, the role-specific campaigns for Product Owner, Scrum Master, and Developer stop being trivia and start being judgment calls you can defend.
3.Role reality
The Scrum Guide is eleven pages. What trips people up is not the length, it is that every line reads as obvious until you meet the situation it was written for.
| Textbook theory | Delivery reality |
|---|---|
| Transparency, inspection and adaptation are three equal pillars. | Transparency fails first, always. If nobody can see the real state of the work, the other two pillars never get a chance. |
| The Scrum Team has three accountabilities. | Most organisations still print job titles on badges. You will spend real energy explaining that a title is not an accountability. |
| The Sprint Goal gives the Sprint a single objective. | Half the Sprints you join will start with five loosely related tickets and no sentence anyone can repeat back accurately. |
| The Daily Scrum is for the Developers to inspect progress. | It quietly turns into a status report to whoever is in the room with the most seniority, unless someone actively protects the format. |
| The Definition of Done is a shared quality standard. | It is usually aspirational on a wall and negotiable under deadline pressure, until someone insists it is not. |
4.Core delivery pillars
Four ideas from the Scrum Guide that are worth carrying into every module after this one.
Measuring something and then changing nothing is theatre. If a Daily Scrum or a Review never changes a plan, ask what it is actually for.
Product Owner, Scrum Master and Developers are accountabilities held without dilution. A steering committee cannot hold half of one.
Product Backlog to Product Goal, Sprint Backlog to Sprint Goal, Increment to Definition of Done. Lose the commitment and the artifact becomes paperwork.
If an event has stopped inspecting its artifact, it has become a habit, not a Scrum event. Naming that gap is the first useful thing you can do in a new team.
5.Where teams lose the thread
Four numbers-free signals that tell you a team has drifted from the framework, months before a retrospective names it.
An issue is known but not raised until the Sprint Review. Transparency has already failed.
Decisions default to seniority in the room instead of the accountable person.
A Sprint with a list of tickets and no sentence a stakeholder could repeat back.
Quality bar moves under deadline pressure without anyone naming the trade-off out loud.
6.Common mistakes and why they fail
Treating accountabilities as job titles
Reading Scrum Master, Product Owner, and Developer as three separate departments instead of three accountabilities inside one team. The Guide explicitly rules out sub-teams and hierarchies within a Scrum Team.
Learning events without their commitment
Memorizing the length of a Daily Scrum or Sprint Review without connecting it to the Sprint Goal, Product Goal, or Definition of Done it exists to protect. This is how teams end up running the ceremony with none of the adaptation.
Skipping straight to the games
Jumping into Foundations or a role campaign before finishing the primer usually means re-learning the same theory later, badly, from a scenario that assumes you already know it.
7.Questions worth asking before you commit time to this
Does Module 0 count toward a certificate?
No. The primer is deliberately certificate-free. It exists to validate core knowledge before you start the role tracks, where certificates of completion are actually earned. Treat it as the entry exam you take on yourself.
How is this different from just reading the Scrum Guide PDF?
The Scrum Guide is dense and assumes context. This primer breaks the same rules into four short lessons with worked examples and a knowledge check, so the theory sticks before you meet it again inside a simulation under time pressure.
I already know Scrum. Can I skip this?
You can, but the most common failure mode in the later campaigns is confidently applying folklore, story point velocity targets, command-and-control facilitation, that never appeared in the actual Guide. Ten minutes here usually surfaces at least one of those gaps.
8.What to remember
- The three pillars of empiricism, stated as decisions, not definitions
- Accountabilities versus job titles, and why the difference matters on day one
- A checklist for spotting when a team has quietly dropped an artifact's commitment
9.Where this sits in the Scrumling course
Start here. Official Scrum theory, in plain language, before you jump into the simulations.
About 21 minutes of lessons and decision scenarios.
- Welcome to Module 0
- Lesson 0.1: The Empirical Foundation
- Lesson 0.2: Accountabilities over Roles
- Lesson 0.3: Events, Artifacts & Commitments
- Lesson 0.4: Where to go from here
Assessment: Module 0 knowledge check