Scrum: Sprints, Roles, Ceremonies, Backlog
If Agile is the mindset, Scrum is by far the most common way teams actually practice it. It's a lightweight framework: work happens in fixed short cycles called sprints, with a few defined roles, a handful of regular meetings, and one prioritized list of everything to do.
Scrum sounds like a lot of jargon at first, but it's a small set of pieces that fit together simply. These are also the exact words you'll hear in your first week on almost any team — so this topic is worth getting solid.
A familiar parallel: a TV writers' room that ships one episode every two weeks. There's a planning meeting at the start, a quick check-in each day, a screening at the end, and a chat about how to work better next time. Swap "episode" for "working software" and that's Scrum.
The Roles
Scrum names three roles. The product owner decides what's worth building and in what order — they own the priorities. The scrum master is a facilitator and coach who keeps the process running smoothly and clears obstacles; crucially, they are not the team's boss. And the developers — the people who actually build the software, often including testers and designers — decide together how much the team can take on. (Older Scrum material calls this group the "development team"; the current guide just says "developers".)
The Artifacts
Scrum tracks work in three things. The product backlog is the single, ordered list of everything the product might need, most important at the top. The sprint backlog is the slice of that list the team commits to for the current sprint. And the increment is the working, potentially-shippable software produced by the end of the sprint. Backlog in, working software out.
The Ceremonies
Four regular events — commonly called "ceremonies" — give a sprint its rhythm; Scrum counts the sprint itself as a fifth event that wraps around the other four. Don't let the word fool you; they're short and practical.
| Ceremony | When | Purpose |
|---|---|---|
| Sprint planning | Start of sprint | Pick what to build this sprint |
| Daily standup | Every day, briefly | The team syncs and surfaces blockers |
| Sprint review | End of sprint | Show the working software to stakeholders |
| Retrospective | End of sprint | Improve how the team works |
The Rhythm
Put together: a sprint is a fixed window, usually one to four weeks, that repeats. Plan at the start, build through the middle with a quick daily sync, then at the end show what you made (the review) and talk about how to do better (the retro) — and immediately start the next sprint. Each sprint ends with something that could ship. That steady, repeating heartbeat is the whole idea: predictable cycles, frequent feedback, constant small improvement.
The Cadence team runs two-week sprints. Priya keeps the product backlog ordered; every morning the four of them stand up for five minutes to sync; at sprint's end they demo to a few real users (the review) and then hold a retro. In one retro they admit their stories keep being too big to finish in a sprint — so they agree to slice them smaller. That tiny adjustment, made because the retro exists, is Scrum doing its job.
- "The scrum master is the team's boss." They're a facilitator and coach who removes obstacles and protects the process — not a manager handing out orders.
- "The daily standup is a status report to a manager." It's for the team to sync with each other and surface blockers, not to justify yourself to someone above.
- "The sprint review and the retrospective are the same meeting." The review is about the product (show the working software); the retro is about the process (how to work better). Different goals.
- "Sprint", "standup", "backlog", and "retro" are words you'll hear on day one of most teams — this topic decodes all of them at once.
- Scrum is the single most common way Agile is actually practiced, so recognizing its pieces helps you fit into the majority of modern teams.
- Its rhythm — plan, build, show, improve, repeat — is a concrete, repeatable version of the iterative mindset from the last topic.
Knowledge Check
What is a "sprint" in Scrum?
- A fixed short cycle, usually one to four weeks, that repeats
- A last-minute push to hurriedly finish absolutely everything before the launch
- The short daily meeting where the team syncs up
- The prioritized list of everything the product needs
What does the scrum master do?
- Facilitates the process and removes obstacles for the team
- Acts as the team's boss, personally assigning everyone their individual tasks
- Decides what features get built and in what order
- Writes most of the software themselves each sprint
What is the product backlog?
- The single ordered list of everything the product might need
- Only the work the team committed to for this sprint
- A list of only the bugs that have ever been reported
- The finished, potentially shippable software produced at the end of a sprint
How does the sprint review differ from the retrospective?
- The review is about the product; the retro is about how the team works
- They are two names for exactly the same meeting
- The review is about process; the retro shows the product
- Both of these meetings happen only at the very start of a sprint, before any work
What is the daily standup for?
- A short meeting for the team to sync and surface blockers
- A daily report each person gives to their manager
- The meeting where the whole sprint's work is planned
- The session where finished software is demoed to customers
You got correct