Scrum Quiz: 12 Questions to Test Your Scrum Knowledge

12 scenarios straight from Sprint life. Do you know what the Scrum Guide actually says — or what your last team just made up? Plain-English answers after every question, no sign-up.

0 / 12 answered

A new hire asks: "So Scrum tells us exactly how to code, test and deploy, right?" According to the Scrum Guide, what is Scrum?

Your new Scrum Master opens the week by assigning tasks to each developer and setting their deadlines. What's off?

Marketing, sales and the CEO all want their feature first. Who is accountable for ordering the Product Backlog and maximizing the product's value?

During Sprint Planning, a manager drops in and tells the team exactly how much work to take on this Sprint. Who should actually decide?

Your team's daily stand-up keeps ballooning into 45 minutes of discussion. How long does the Scrum Guide timebox the Daily Scrum?

A department head asks to join the Daily Scrum so developers can "report progress to me every morning." What is the Daily Scrum actually for?

The team wants a six-week "mega Sprint" to fit one big feature in. What does the Scrum Guide say about Sprint length?

Stakeholders want to see the working Increment and give feedback that could reshape the backlog. Which event is built for that?

The Sprint just ended. The team gathers — no stakeholders — to talk about what dragged them down and how to work together better. Which event is this?

Q10

A developer says a feature is "done — I just haven't tested it yet." Which Scrum commitment settles what 'done' means?

Q11

A team hides its bug count so the burndown chart looks healthy. Which pillar of empiricism just collapsed?

Q12

Your team wants the five Scrum values on a poster, but one impostor snuck into the draft. Which of these is NOT a Scrum value?

Answer all 12 questions to see your result 👆

Scrum in 12 lines (cheat sheet)

Scrum: A lightweight framework for complex problems, built on empiricism — not a step-by-step methodology.
Sprint: The container for all work: one month or less; a new one starts immediately.
Product Owner: Accountable for maximizing product value; owns and orders the Product Backlog.
Scrum Master: Accountable for establishing Scrum; a servant leader — not a project manager.
Developers: Accountable for a usable Increment every Sprint; plan their own work.
Sprint Planning: Sets what and how for the Sprint; max 8 hours for a one-month Sprint.
Daily Scrum: 15 minutes, for Developers — re-plan the day toward the Sprint Goal.
Sprint Review: Show the Increment, gather stakeholder feedback; max 4 hours.
Sprint Retrospective: The team improves how it works together; max 3 hours.
Product Backlog → Product Goal: The ordered to-do list, committed to a long-term goal.
Sprint Backlog → Sprint Goal: This Sprint's plan, committed to a single focus.
Increment → Definition of Done: No DoD, no 'done' — and nothing releasable.

What is Scrum, actually?

Scrum is defined in The Scrum Guide, written and maintained by Ken Schwaber and Jeff Sutherland. The 2020 edition calls it a lightweight framework that helps people, teams and organizations generate value through adaptive solutions to complex problems. It stands on empiricism — deciding from observed facts — and lean thinking, held up by three pillars: transparency, inspection and adaptation.

Its roots go back to 2001, when 17 software practitioners wrote the Manifesto for Agile Software Development, with values like 'responding to change over following a plan.' Scrum turns that idea into a heartbeat: Sprints of one month or less, each ending with a usable Increment, real feedback and a course correction — many small bets instead of one giant one.

In the wild, though, a lot of teams run Scrum in name only: the Scrum Master acts as a project manager, the Daily Scrum becomes a morning status report, and 'agile' means waterfall sliced thin. Those are exactly the misconceptions this quiz pokes at — because they're the difference between doing Scrum and just saying it.

The 12 questions cover the whole official skeleton: the three accountabilities (Product Owner, Scrum Master, Developers), the five events and their timeboxes, the three artifacts with their commitments, the five values, and the three pillars of empiricism.

FAQ

What are the 3 Scrum roles?

Product Owner (maximizes product value, orders the Product Backlog), Scrum Master (establishes Scrum, serves the team) and Developers (deliver a usable Increment each Sprint). The 2020 Scrum Guide calls them accountabilities.

How long is a Daily Scrum?

15 minutes, every working day. It belongs to the Developers — it's for planning the day, not reporting to managers.

How long can a Sprint be?

One month or less, and a new Sprint starts immediately after the previous one ends.

Is the Scrum Master the same as a project manager?

No. A Scrum Master is a servant leader who helps the team run Scrum and removes obstacles — they don't assign tasks or set deadlines.

What are the 5 Scrum values?

Commitment, Focus, Openness, Respect and Courage — the soft core that keeps the framework from becoming empty ritual.