Learn to spot the Scrum anti-patterns that quietly hollow out delivery — Scrum-but, proxy Product Owners, boss-mode Scrum Masters, mini-Waterfall Sprints and status-meeting Dailies — and fix each one by returning to Scrum's real purpose. Build a diagnostic checklist and lead the fixes without blame.
Watch the free preview
Scrum-but — keeping the words, losing the point — free to watch, no account needed.
What you'll learn
- Identify the most common Scrum anti-patterns across roles, events and artifacts
- Explain why each anti-pattern persists and which part of Scrum it undermines
- Diagnose a real team's way of working against Scrum's actual purpose
- Redesign mini-Waterfall Sprints into a single cross-functional Sprint that produces a Done Increment
- Build and run a Scrum Anti-Pattern Diagnostic Checklist and lead the fixes without blame
Syllabus
What Anti-Patterns Are and Why They Persist
Scrum-but — keeping the words, losing the pointFree preview
Why good teams drift — the forces behind anti-patterns
Role and Artifact Anti-Patterns
The proxy Product Owner and the boss-mode Scrum Master
The hollow Definition of Done and the velocity weapon
Event and Flow Anti-Patterns in Real IT Work
Mini-Waterfall Sprints and Sprint Goal-less Sprints
Case study — the plan, build, test trio called Scrum
Making the Fixes Stick
Building the Scrum Anti-Pattern Diagnostic Checklist
Leading the fixes without blame