What you practise in this lab
Free Scrum lab in simple English: run Sprint Planning for a real team as the Scrum Master. Set the Sprint Goal, select the work, handle a stakeholder and the timebox, and see the Scrum Guide logic behind each decision.
- Sprint Planning inputs
- Why: create the Sprint Goal
- What: select the work
- How: who decides how the work is done
- A visitor wants his report in the Sprint
- The Sprint Planning timebox
Scrum Guide rules used in this lab
- Scrum Guide: the more the Developers know about “their past performance, their upcoming capacity, and their Definition of Done”, the more confident they will be in their Sprint forecasts.
- Scrum Guide: the Product Owner proposes how the product could increase its value, and “the whole Scrum Team then collaborates to define a Sprint Goal”. The Sprint Goal must be finalized before the end of Sprint Planning.
- Scrum Guide: “No one else tells them how to turn Product Backlog items into Increments of value.” How this is done is at the sole discretion of the Developers.
- Scrum Guide: for Product Owners to succeed, “the entire organization must respect their decisions”. Those wanting to change the Product Backlog can do so by trying to convince the Product Owner.
- Scrum Guide: “Work planned for the first days of the Sprint by the Developers is decomposed by the end of this event, often to units of one day or less.” Sprint Planning is timeboxed to a maximum of eight hours for a one-month Sprint; shorter Sprints usually need less.
Prepare with the free Scrum course, then test yourself with the free Scrum Master practice test.