Map Scrum's three accountabilities, five events and three artifacts, and how they fit into one sprint.
Why it matters
Scrum is the most widely used agile framework. If you work on or with a software or product team, you will hear its words every day: sprint, product owner, backlog, stand-up, retro. Knowing exactly what each one means, and what it does not mean, lets you take part from day one and spot when a team's "Scrum" has drifted.
Scrum is defined in The Scrum Guide by its creators, Ken Schwaber and Jeff Sutherland. The current version (2020) is free and under 20 pages at scrumguides.org. Checked on 2026-10-23. This lesson follows it.
The idea in one paragraph
Scrum is a lightweight framework for solving complex problems in short cycles called sprints, each one month or less (two weeks is common). In every sprint a small team turns the most valuable items from a backlog into a usable increment, shows it to stakeholders, and reflects on how to work better. Scrum rests on empiricism: transparency, inspection and adaptation. You make the work visible, check it often and change course based on what you see.
Three accountabilities
A Scrum Team is small, typically 10 or fewer people, with no sub-teams or hierarchy. It has three accountabilities:
| Accountability | Owns | Northside Sports Centre example |
|---|---|---|
| Product Owner | Maximising the value of the product; the Product Backlog and its order | The centre's membership manager, who decides that court booking comes before class booking |
| Scrum Master | The team's effectiveness and how well Scrum is understood and used | A coach who removes blockers, facilitates events and helps the organisation work with the team |
| Developers | Creating a usable increment every sprint | The designers, programmers and testers building the app |
"Developers" means everyone doing the work, not only programmers. A Scrum Master is not a project manager handing out tasks, and the Product Owner is one person, not a committee, though they can take input from many stakeholders.
Five events
| Event | Purpose | Timebox (one-month sprint) |
|---|---|---|
| The Sprint | The container for all the other events | One month or less |
| Sprint Planning | Decide why this sprint is valuable (Sprint Goal), what can be done and how | Up to 8 hours |
| Daily Scrum | Developers inspect progress towards the Sprint Goal and adjust the plan | 15 minutes |
| Sprint Review | Inspect the increment with stakeholders and adapt the Product Backlog | Up to 4 hours |
| Sprint Retrospective | Inspect how the team worked and plan improvements | Up to 3 hours |
For shorter sprints the events are usually shorter. A two-week sprint might have about four hours of planning, a 15-minute Daily Scrum each day, a two-hour review and a 90-minute retrospective.
Note what the Daily Scrum is not: a status report to a manager. The guide removed the "three questions" (what did I do yesterday, what will I do today, any blockers) as a requirement in 2020; teams can use any structure that focuses on the Sprint Goal.
Three artifacts and their commitments
Each artifact has a commitment that gives it focus:
| Artifact | What it is | Commitment |
|---|---|---|
| Product Backlog | An ordered list of everything that might be needed in the product | Product Goal: the long-term objective |
| Sprint Backlog | The Sprint Goal, the items chosen for the sprint and the plan to deliver them | Sprint Goal: the single objective for the sprint |
| Increment | A usable step towards the Product Goal, added to all previous increments | Definition of Done: the quality standard every increment meets |
The Definition of Done is the team's shared checklist: for example "code reviewed, tests pass, accessible, deployed to the test environment, product owner has seen it". An item that does not meet it is not part of the increment and goes back to the Product Backlog.
One sprint, end to end
Day 1 Sprint Planning: goal "A member can book and cancel a court on their phone"
Days 1-10 Daily Scrum each morning; Developers build, test and integrate
Product Backlog Refinement runs alongside (not an event, but ongoing)
Day 10 Sprint Review: demo to the centre manager and two members; backlog updated
Day 10 Sprint Retrospective: team agrees one improvement for next sprint
Day 11 Next sprint starts with Sprint Planning
Common mistakes
- The Scrum Master as boss who assigns tasks. Developers decide how to do the work.
- A proxy or committee Product Owner with no authority to say no.
- Skipping the retrospective when busy, which removes the improvement loop.
- Sprint Review as a one-way demo with no stakeholder feedback and no change to the backlog.
- Extending the sprint to finish work. The timebox is fixed; unfinished work returns to the backlog.
Quick recap
- Scrum delivers a usable increment every sprint of one month or less, based on transparency, inspection and adaptation.
- Three accountabilities: Product Owner, Scrum Master, Developers.
- Five events: Sprint, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective.
- Three artifacts with commitments: Product Backlog (Product Goal), Sprint Backlog (Sprint Goal), Increment (Definition of Done).