What the Scrum Guide primer actually covers
Most Scrum training starts with the events and artifacts, then treats the underlying theory as an afterthought. This module reverses the order on purpose. Before you touch a simulation, you need to understand why Scrum inspects and adapts at all: because the work is complex, the requirements are not fully knowable up front, and any plan written before the first Sprint is a guess dressed up as a schedule. The three pillars, transparency, inspection, and adaptation, are not slogans. They are the mechanism that makes every other rule in the Scrum Guide make sense.
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.
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.
Mistakes teams make with this material
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.
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.
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.
Questions people ask
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.
A question from this module's assessment
One sample question with the reasoning, so you can judge the level before you start. The rest of the assessment stays inside the module.
A developer hides a slipping API integration until the Sprint Review to avoid distracting the team. Which pillar of empiricism has been broken FIRST?
- Adaptation
- Transparency
- Inspection
- Focus
Transparency fails first. Without it, the team cannot inspect, and therefore cannot adapt. Hiding the slip denies the team any chance to protect the Sprint Goal.