The Scrum Framework: Roles, Events, and Artifacts
This domain, The Scrum Framework: Roles, Events, and Artifacts, tests precise mechanics. You must know the accountabilities, event purposes and timeboxes, artifact commitments, and the rules that keep the framework coherent.
Roles, events, and artifacts
- The Scrum Team is one Product Owner, one Scrum Master, and Developers. It is cross-functional and self-managing; no sub-teams or manager layer inside it. The Product Owner maximizes product value and manages the Product Backlog. Developers create the Increment. The Scrum Master establishes Scrum and enables effectiveness.
- The Sprint is the container event, one month or less. Sprint Planning is timeboxed to 8 hours maximum for a one-month Sprint; Daily Scrum is 15 minutes for Developers; Sprint Review is 4 hours maximum; Sprint Retrospective is 3 hours maximum. Shorter Sprints usually use shorter timeboxes.
- Artifacts and commitments: Product Backlog -> Product Goal; Sprint Backlog -> Sprint Goal; Increment -> Definition of Done. The Definition of Done is a formal description of the Increment’s quality state.
Worked example
A two-week Sprint team holds a 90-minute Sprint Review, shows a demo, and collects no stakeholder feedback. The timebox is within limits, but the event’s purpose is to inspect the outcome and adapt the Product Backlog. Reasoning: a demo alone is not inspection if stakeholders cannot discuss value and next steps. The Scrum Master coaches the Product Owner to invite relevant stakeholders and structure the Review around the Product Goal and Increment, not a status slide deck.
Traps that cost marks
- Saying the Scrum Master assigns tasks or the Product Owner manages the team.
- Treating the Sprint Review as an approval gate or the Daily Scrum as a report to the Scrum Master.
- Listing backlog refinement as a formal event; it is an ongoing activity.
- Forgetting that the Definition of Done applies to every Increment.