Scrum for beginners: the 10-minute intro
A plain-English introduction to Scrum for absolute beginners. Covers the roles, the events, the artifacts, and the single idea that ties them all together.
Scrum is a way for a small team to build a product one small piece at a time, checking in with reality often enough to change direction cheaply. That is it. Everything else is scaffolding.
The one idea to hold onto
Scrum is empirical. Empirical means decisions come from observing reality, not from a plan made in advance. Every Scrum event exists to inspect something real and adapt from it.
Three accountabilities
- Product Owner, decides what the team builds next, in what order, to maximise value.
- Scrum Master, coaches the team on Scrum, removes impediments, protects the Sprint.
- Developers, the people who actually build the Increment. Cross-functional and self-managing.
Five events
- Sprint, the container. One to four weeks. A fresh one starts the moment the last one ends.
- Sprint Planning, the team picks what to build this Sprint and why.
- Daily Scrum, 15 minutes for the Developers to inspect progress toward the Sprint Goal.
- Sprint Review, the team shows the Increment to stakeholders and gets feedback.
- Sprint Retrospective, the team inspects how it worked and picks one thing to improve.
Three artifacts
- Product Backlog, everything the team might build, ordered by the Product Owner.
- Sprint Backlog, what the team plans to build this Sprint, plus how.
- Increment, a usable, potentially releasable slice of the product.
Where beginners get stuck
The framework looks like a set of meetings. It is actually a set of decisions. The meetings only work when the team uses them to make real calls, what to build, whether to keep going, what to change. If your Sprint Planning is a status meeting, you are doing Scrum's shape without its substance.
The fastest way to get past this is to feel the decisions yourself. Scrumling's role games take you through them in under six hours, free.