What you practise in this lab
Free advanced Scrum lab in simple English: audit a broken Daily Scrum, save a Sprint Goal at risk, decide who can cancel a Sprint, and handle a manager who wants a Gantt chart. Your decisions move the team health meters.
- Audit the Daily Scrum
- Find the root cause
- Coach the team without taking over
- The Sprint Goal hits a wall
- Who can cancel a Sprint?
- The manager wants a Gantt chart
- Hand it back to the team
Scrum Guide rules used in this lab
- Scrum Guide: the Daily Scrum is “a 15-minute event for the Developers of the Scrum Team”. Its purpose is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary.
- Scrum Guide: “The Developers can select whatever structure and techniques they want”, as long as the Daily Scrum focuses on progress toward the Sprint Goal and produces an actionable plan for the next day of work.
- Scrum Guide: the Scrum Master serves the Scrum Team by “coaching the team members in self-management and cross-functionality”, and by ensuring that all Scrum events take place and are positive, productive and kept within the timebox.
- Scrum Guide: during the Sprint, “no changes are made that would endanger the Sprint Goal”, and scope may be clarified and re-negotiated with the Product Owner as more is learned.
- Scrum Guide: “Only the Product Owner has the authority to cancel the Sprint.” A Sprint could be cancelled if the Sprint Goal becomes obsolete.
- Scrum Guide: the Sprint Backlog is “a highly visible, real-time picture of the work” that the Developers plan to accomplish during the Sprint.
- Scrum Guide: Scrum Teams are self-managing, “meaning they internally decide who does what, when, and how.”
Prepare with the free Scrum course, then test yourself with the free Scrum Master practice test.