People & Crisis in Scrum
Scrum doesn't fail because people don't understand the framework. Scrum fails because people are people.
The Scrum Master who asks "what did you do yesterday?" instead of "what's blocking you today?" isn't being lazy — they've just been trained by a culture of status reporting. The Product Owner who insists everything is Priority 1 isn't unreasonable — they're managing stakeholder pressure the only way they know. The team that has the same retrospective action for three months running isn't lazy — they've stopped believing retros change anything.
This module is about the human system behind the Scrum framework — and how to intervene in it.
What You'll Learn in This Module
- Why Daily Scrums become status reports and the facilitation moves that break the pattern
- How to identify the three most common Daily dysfunction types
- The scope/time/quality negotiation triangle and how to use it with a demanding PO
- Healthy tension techniques that keep the PO–Team relationship productive, not adversarial
- What makes a retrospective action stick (and why most don't)
- Three high-impact retrospective formats beyond the standard sticky-note exercise
Module Lessons
- Saving the Daily Scrum — Why Dailies degrade; three dysfunction patterns; facilitation techniques that restore the meeting's purpose
- PO vs Team: The Art of the Impossible Negotiation — Scope/time/quality triangle; escalation paths; how to say "no" without damaging the relationship
- Retrospectives That Actually Work — Why retros stagnate; the 4Ls, Fishbone, and Start/Stop/Continue formats; how to measure whether a retro worked
Complete all three lessons and earn the Team Diplomat badge. You'll become the person teams call when things get hard.