Learn Scrum by making decisions.
Sprint Panic! puts you inside four simulated Sprints. Choose a Sprint Goal, manage flow, respond to uncertainty, inspect outcomes, and adapt. No installation, no account, no server.
Scrum gets interesting when the Sprint gets messy.
Memorizing events, artifacts, and accountabilities is easy. Deciding what to do when capacity changes, technical work emerges, a dependency releases a security patch, or too much work is in progress is harder. Sprint Panic! is built around those decisions.
🎯 Protect the Sprint Goal
Adapt the plan as you learn without treating the Sprint Backlog as a frozen contract.
🗣️ Use the Daily Scrum
Inspect progress toward the Sprint Goal and decide whether the plan actually needs to change.
🛠️ Make hidden work visible
Defects, integration work, security updates, and other discoveries can become explicit Sprint Backlog work.
✅ Respect Done
A nearly finished item with a blocking defect is still not Done and does not become part of a usable Increment.
🌊 Experience flow
Experiment with WIP and swarming while keeping clear that these are supporting practices, not mandatory Scrum rules.
⚡ Respond to uncertainty
Illness, outages, flaky tests, library releases, security fixes, and stakeholder feedback change the situation.
The scenario
Your team is building an interplanetary pizza-delivery application.
“Enable a person on Mars to choose, pay for, and track a pizza with confidence.”
Play it. Discuss it. Break it. Improve it.
The simulation is intentionally simplified. Its value is in the discussion that follows: Why was the Sprint Goal achieved or missed? Which work should have become visible? When did WIP hurt flow? Which feedback should alter the Product Backlog?