Scrum: roles, events, artefacts
Scrum according to the 2020 Scrum Guide: the three accountabilities, the events and their maximum length, the artefacts and their commitment, the three pillars, and the most frequent drifts.
- 30 cards
- 5 topics
- Free
The outline, topic by topic
Each topic is weighted the way the exam weighs it.
- Concepts
- Questions
- Sort and link
- Scenarios
- Understand
A few cards from the deck
Scrum: what is it?
Show the answer
A lightweight framework in which a small team delivers value in increments, in short fixed-length cycles, inspecting its work and adapting.
It is a framework, not a complete method: it sets roles, events and artefacts, and leaves the team free to choose its technical practices.
Who has the authority to cancel a Sprint?
- The Product Owner, if the Sprint Goal has become obsolete
- The Scrum Master, as soon as an impediment blocks the team
- The Developers, when they judge they cannot finish everything
- The customer, when their priorities change during the Sprint
Show the answer
The Product Owner, if the Sprint Goal has become obsolete
Only the Product Owner can cancel a Sprint, and only if the goal no longer makes sense. Not finishing everything or a changed priority is no reason: the scope is renegotiated with them.
The three pillars of Scrum are transparency, … and ….
Show the answer
The three pillars of Scrum are transparency, inspection and adaptation.
The work is made visible, examined often, then the course is corrected. The Scrum events are so many occasions to inspect and adapt.
Product Owner: what is it?
Show the answer
The accountability of one person: maximising the value of the product and managing the Product Backlog, which they order and make transparent.
It is one person, not a committee: they may delegate the work but stay accountable for the backlog's order. They develop and communicate the Product Goal, which is the Product Backlog's commitment.
The Daily Scrum lasts 45 minutes and everyone reports to the project manager. What should be done?
- Move it to once a week so the project manager can attend it for longer
- Replace the meeting with a written report that everyone sends each evening
- Keep the 45 minutes but have the stakeholders speak first each day
- Bring it back to 15 minutes among the Developers, aimed at the Sprint Goal
Show the answer
Bring it back to 15 minutes among the Developers, aimed at the Sprint Goal
The Daily Scrum is the Developers synchronising among themselves to plan their day, not a hierarchical report. It stays short, daily and driven by the Sprint Goal.