LEARN. PRACTICE. GROW.Concept and mechanism
Prepare Sprint Planning with a value proposition, understandable work, and capacity information. If someone is on L3 rotation, do not count them as fully available for new capabilities. Discuss a coherent goal and plausible work selection; break down enough to begin and adapt the plan as learning occurs. During the Daily Scrum, the practical question is whether current work still leads toward the goal and what needs to change. Detailed individual reports are not necessary to answer that. If two people need to diagnose a timeout, they can explore it afterward without turning the whole team’s discussion into a long troubleshooting session.
Guided application
At the review, bring usable evidence and people able to discuss its effect: an operator may discover that new information arrives too late for the daily close. Use that observation in future choices. During the retrospective, inspect the way of working. If a runbook repeatedly fails at handover, an experiment could ask APS to execute its steps in a safe environment before the next delivery. Define an owner, evidence, and review point. Removing this discussion may retain recurring failures, hide collaboration obstacles, and delay quality improvements. A task change does not automatically cancel the Sprint. When the Sprint Goal itself becomes obsolete, cancellation authority belongs to the Product Owner.
An incident can consume capacity and require plan renegotiation even when the goal remains relevant.
Common pitfalls
Daily as a manager report; review as slides; retrospective without action; initial plan as an immutable promise.
Related topics: Facilitation and support approaches · Group decisions and useful closure
Each event should produce understanding or adaptation that helps the next decision.
Reference: The Scrum Guide · CSM learning objectives January 2022 (formatted February 2024), current linked syllabus; Scrum Guide November 2020; no numbered exam revision published