Scrum Mastery Scenarios
Scenario 1: The "Fragile" Sprint Goal
PSM II Challenge
Fatma (PO) suggests the Sprint Goal should be "Complete all selected items" because the backlog items are too diverse.
The Question: As Noor (SM), how do you coach the team? Why is "completing all items" a dangerous anti-pattern?
Coaching Path: Explain that a Sprint Goal must provide flexibility. If it's just a checklist, the team loses focus if a single item hits a technical blocker.
Key Advice: Help the team find the "Why" behind the Sprint. If they can't find one common goal, they might be multi-tasking too much, which violates the Scrum value of Focus.
Key Advice: Help the team find the "Why" behind the Sprint. If they can't find one common goal, they might be multi-tasking too much, which violates the Scrum value of Focus.
Scenario 2: The "Status" Daily Scrum
Facilitation Role
Developers are reporting status to the SM instead of re-planning for each other. The meeting ends in 12 minutes but no adaptation happens.
The Question: The meeting was under the 15-minute time-box. Is your job as SM done? What coaching is needed?
Coaching Path: No, the job isn't done! The goal is Inspection and Adaptation of the Sprint Backlog, not a status report.
Key Advice: Coach the Developers that the Daily Scrum is their plan for the next 24 hours. Physically move out of the circle to encourage them to communicate with each other.
Key Advice: Coach the Developers that the Daily Scrum is their plan for the next 24 hours. Physically move out of the circle to encourage them to communicate with each other.
Scenario 3: The "Incomplete" DoD
Quality Standards
Fatma asks the team to show a feature that works but hasn't passed the mandatory "automated tests" in the DoD.
The Question: What do you say to Fatma and the Developers? What is the risk of showing "undone" work?
Coaching Path: Uphold the Scrum Guide. An item is only an Increment if it meets the Definition of Done (DoD).
Key Advice: Presenting "undone" work destroys Transparency. It creates a false sense of progress and builds Technical Debt that will slow the team down in future Sprints.
Key Advice: Presenting "undone" work destroys Transparency. It creates a false sense of progress and builds Technical Debt that will slow the team down in future Sprints.