Do You Know the Scrum Guide — or Just the Ceremonies?

Published: September 25, 2026
Tags: Scrum, Scrum Guide 2020, Cargo Cult Agile, Scrum Master, Certification

---

The Standup Litmus Test

Try this at your next Daily Scrum. Before the meeting starts, ask the room one simple question: "Who here has actually read the 2020 Scrum Guide — cover to cover?"

Expect silence. Maybe a nervous laugh. Possibly one person who read the 2017 edition years ago and assumes nothing changed.

Here's the strange part: the ceremonies are everywhere. According to the 17th Annual State of Agile Report, Scrum remains the dominant team-level methodology — 63% of agile teams run it (and that figure was closer to 87% in the previous edition). Standups, sprint reviews, retrospectives, backlog refinement — the rituals survived contact with the real world just fine.

Yet the same report lands the punchline: only 11% of agile users describe themselves as "very satisfied" with how agile works in their organization. The report's own diagnosis? Lack of understanding and inadequate training are among the top barriers.

Sixty-three percent adoption. Eleven percent satisfaction. The ceremonies survived. The understanding didn't.

---

Cargo-Cult Scrum

There's a name for this pattern: cargo-cult Scrum — performing the visible rituals while missing the invisible theory that makes them work. You'll recognize it instantly if you've lived it:

• The status-report standup. Fifteen minutes where each person reports to the Scrum Master what they did yesterday. Except the Daily Scrum isn't a status meeting — it's a planning event for the Developers, and the Scrum Master doesn't even have to attend.
• The retrospective that changes nothing. Everyone vents, someone writes sticky notes, the team adjourns — and the same complaints resurface next sprint. Inspection without adaptation is just theatre.
• Product Owner by committee. Three stakeholders, a Slack channel, and a Jira board anyone can edit. The Guide is blunt on this one: the Product Owner is one person, not a committee.
• "Scrum-but" as a badge of honor. "We do Scrum, but we skip the retro." "We do Scrum, but our sprints are six weeks." Each carve-out sounds pragmatic. Collectively they describe a process that is no longer Scrum.

None of this happens because teams are lazy or cynical. It happens because Scrum is almost never learned from the source. It's learned secondhand — from a colleague's onboarding, a training slide deck from 2018, a blog post summarizing a blog post. Each hand-off drifts further from the thirteen pages that define the thing.

This isn't pedantry. The Guide itself issues the warning, in plain language: "Changing the core design or ideas of Scrum, leaving out elements, or not following the rules of Scrum, covers up problems and limits the benefits of Scrum, potentially even rendering it useless."

Read that again. The people who invented Scrum are telling you that performing the events without the theory doesn't just underperform — it covers up problems. The low satisfaction numbers aren't a failure of Scrum. They're a failure of teams running a version of Scrum that exists only in folk memory.

---

What's Actually in the Guide — and What Isn't

The 2020 Scrum Guide is roughly thirteen pages. Shorter than most sprint-planning slide decks. And yet most practitioners can't name its basic structure.

Quick test — no Googling:

• Can you name all five Scrum values?
• Do you know why the Guide says "accountabilities" and not "roles" — and how many there are?
• Each of the three artifacts carries a commitment. Can you pair them? Product Backlog → ? Sprint Backlog → ? Increment → ?
• What are the three pillars of empiricism the whole framework stands on?

(Commitment, Focus, Openness, Respect, Courage. Three accountabilities. Product Goal, Sprint Goal, Definition of Done. Transparency, Inspection, Adaptation. If you stumbled on any of those, keep reading.)

But here's the twist that separates people who read the current Guide from people who absorbed Scrum by osmosis: the most reliable tells are things the Guide removed.

The 2020 update — released on Scrum's 25th anniversary — deliberately stripped out prescriptive detail. According to Scrum.org's own coverage, the removals include:

• The three Daily Scrum questions. "What did I do yesterday? What will I do today? Any impediments?" — gone. It was always an example, never a requirement, and it hasn't been in the Guide since 2020. Teams still reciting it like scripture are performing the 2017 edition.
• The 10% refinement cap. The old rule that refinement "usually consumes no more than 10% of the Development Team's capacity" no longer exists. Anyone still quoting it is citing folklore.
• "Self-organizing." Replaced by "self-managing" — a deliberate strengthening. Self-managing teams decide who does the work, how, and what to work on. One word apart, a philosophy apart.
• The "Development Team" as a separate unit. The 2020 Guide collapsed it into one Scrum Team — Product Owner, Scrum Master, Developers — specifically to kill the "us vs. them" dysfunction of a team-within-a-team.

If your Scrum vocabulary is 2017, your Scrum is folklore. And folklore is very hard to defend in a job interview — or to a team you're supposed to be coaching.

Wondering how much of that you would have caught? The Scrum Master Foundation exam is free, 30 questions, an hour of your time — an honest answer is one click away.

---

Why Self-Assessment Fails Exactly Here

Scrum has a uniquely cruel property: it feels known. Thirteen pages, five events, a handful of terms — everyone who's sat through six months of standups believes they could pass a test on it. Confidence is cheap when there's no benchmark to check it against.

This is the Dunning-Kruger problem wearing an agile hoodie. The gap only becomes visible at the worst possible moments:

• A Scrum Master interview where the interviewer has read the Guide and asks what changed in 2020.
• A coaching conversation where you correct a team's practice — and they ask which part of the Guide says that.
• A CV that claims "deep Scrum expertise" next to a hiring manager's quick screening quiz.

"I think I know Scrum" is a feeling. A score is a fact. The only way to convert the first into the second is to sit in front of questions you didn't write and find out where you actually stand — on the values, the accountabilities, the commitments, the events, and yes, the things that were removed.

That number does two things a vague feeling never can. If it's high, it converts quiet competence into something you can put on a CV and defend in an interview. If it's low, it hands you a map — these specific domains, these specific gaps — instead of a creeping suspicion you can't act on. Either outcome beats not knowing.

---

Prove It Before Your Next Retro

The ProvedExpert Scrum Master Foundation exam exists for exactly this moment. It's free to take — 30 questions, 60 minutes, 70% to pass — and it measures your knowledge of the Scrum framework as the Guide actually defines it, not as your team's folklore remembers it.

Take it this week. Either you pass and the imposter syndrome was noise, or you discover the specific gaps — and that's worth more than another certification-prep bookmark you'll never read.

Clear Foundation and the ladder continues: the Scrum Master Professional exam for practitioners who coach teams, and Scrum Master Expert for those operating at organizational scale. Each rung is a benchmark, not a guess.

And because knowing the framework is only half the Scrum Master's job — you lead people you have no authority over, every single day — the natural pairing is CourseThread's Leading Without Authority email course: seven days on influence without a title. Learn the persuasion skills there; prove the framework knowledge here.

---

ProvedExpert assesses what you actually know — whether you learned it from formal training, the Guide itself, or ten years of real sprints. The ceremonies might be lying to you. A benchmark won't.