The Scrum Guide is famously short — under 14 pages. But each role and event has a specific purpose, a time-box, and a few failure modes that recur in every team. This is the working reference: what each thing is for, who attends, and how it goes wrong.
← Back to Methodologies & SDLC| Role | Owns | Common pitfall |
|---|---|---|
| Product Owner | Product backlog, ordering, value maximization | Treated as a backlog secretary, not a decision-maker. |
| Scrum Master | Effectiveness of the team and Scrum adoption | Acts as a project manager or status-reporter. |
| Developers | Creating the increment and the Definition of Done | Externalize commitment ("the PO promised it") instead of owning it. |
| Event | Time-box (2-week sprint) | Purpose |
|---|---|---|
| The Sprint | 2 weeks | The container for everything else. A mini-project with a goal. |
| Sprint Planning | ≤ 4 hours | Pick the Sprint Goal; pick backlog items; build the plan. |
| Daily Scrum | 15 minutes | Devs synchronize on progress toward the Sprint Goal & adjust. |
| Sprint Review | ≤ 2 hours | Demo the increment; collect stakeholder feedback; adapt the backlog. |
| Retrospective | ≤ 1.5 hours | Inspect how the team works; commit to one or two improvements. |
Time-boxes are maximums, not targets. A 5-minute Daily Scrum that achieves the sync is fine.
| Artifact | Commitment | What it answers |
|---|---|---|
| Product Backlog | Product Goal | What is this product trying to become? |
| Sprint Backlog | Sprint Goal | What are we trying to achieve this sprint? |
| Increment | Definition of Done | What does "finished" look like? |
DoD is the team's quality contract with themselves. Loose DoD = "done-ish" = inflated velocity that hides real work.