Study guides / CAPM: Certified Associate in Project Management / Scrum roles, events & artifacts
Scrum roles, events & artifacts
CAPM: Certified Associate in Project Management · quick review
The Scrum framework as the Scrum Guide defines it: three accountabilities, five events and three artifacts, each with a commitment.
The rules
- Product owner: maximizes value; owns and orders the product backlog. Scrum master: coaches the team and organization in Scrum, removes impediments. Developers: create the increment and own the sprint backlog. A Scrum team is typically 10 or fewer people.
- Sprint: a fixed timebox of one month or less that contains all other events. Only the product owner can cancel a sprint.
- Sprint planning (up to 8 hours for a one-month sprint): why (sprint goal), what, and how. Daily scrum: 15 minutes, for developers, inspecting progress toward the sprint goal.
- Sprint review: inspect the increment with stakeholders and adapt the backlog. Sprint retrospective: inspect how the team worked and plan improvements.
- Artifacts and commitments: product backlog → product goal; sprint backlog → sprint goal; increment → definition of done.
- Work that doesn't meet the definition of done can't be released or shown as done; it returns to the product backlog.
Common traps
- The daily scrum is not a status meeting for managers.
- The scrum master doesn't assign tasks or own the backlog.
- The sprint review looks at the product; the retrospective looks at the process.
How it's tested
Who does what, which event fits a situation, and matching artifacts to commitments.
Practise it
The full lesson, worked examples and practice questions are in Tickmark, where every answer choice is explained.
Open the full lesson