Scrum Framework
3
Roles
Product Owner, Scrum Master, Developers
5
Events
Sprint, Planning, Daily, Review, Retro
3
Artifacts
Product Backlog, Sprint Backlog, Increment
the sprint cycle · one loop per sprint, forever
Sprint Cycle
how to read this
- › The Sprint is the container in the middle. Everything else happens inside one Sprint, then repeats.
- › Start with Sprint Planning (top) — the team picks work and agrees on a Sprint Goal.
- › Daily Scrum (right) — the team syncs for 15 minutes every day to inspect and adapt.
- › Sprint Review (bottom) — show the working increment to stakeholders and collect feedback.
- › Retrospective (left) — the team inspects their own process and picks one improvement for next sprint.
- › Then the loop restarts. Same rhythm, forever.
Three Roles · Three Artifacts
Roles
Product Owner
Maximizes value. Owns the Product Backlog.
Scrum Master
Servant leader. Removes impediments.
Developers
Self-organizing, cross-functional.
Artifacts
Product Backlog
Ordered list of everything. PO owns.
Sprint Backlog
Committed items + plan. Team owns.
Increment
Sum of done items. Meets DoD.
Exam Traps
The Scrum Master does not assign work
The Development Team self-organizes and pulls work from the sprint backlog. Any answer that has the Scrum Master dispatching tasks is wrong.
The Product Owner owns what, not how
The PO prioritizes the backlog and defines acceptance criteria. How the team builds the solution is the developers' decision. PO overriding technical choices is a trap.
The Daily Scrum belongs to the developers
The Scrum Master may attend but does not run it, report to stakeholders in it, or turn it into a status meeting for management. It is a team sync for the team.
Sprint length is fixed, not elastic
You choose a sprint length at the start and keep it. Stretching a sprint to finish unfinished stories is a trap answer. Move the work to the next sprint instead.
Review is product, retro is process
Sprint Review inspects the increment with stakeholders. Retrospective inspects the team process. Do not confuse them.
Definition of Done is binary
A story is either Done or not Done. No "80% done" in Scrum. Incomplete work returns to the backlog.
The PO decides which songs to rehearse next based on the upcoming show. They set priority and tell the band what the audience wants.
The SM removes impediments. Bad mic, broken amp, argument between drummer and bassist — the SM handles it. They do not play an instrument or tell the band how to play.
The band members are cross-functional, self-organizing, and collectively accountable. They figure out arrangement and technique together.
At the end of the week the band plays the setlist for friends (Sprint Review). Then the band talks about how rehearsal went and what to change next week (Retrospective).
Ready to test your PMP knowledge?
1,800 practice questions written by certified professionals.
Start Practicing PMP