Your Scrum Master Is Deceiving You... and You Know It!
summary
Examines how some Scrum Masters and agile coaches have turned Scrum into performative rituals—using techniques like “kudo-boxes,” “powerful questions,” and vague notions of increasing team velocity—while neglecting practical engineering practices. Argues that real agile results come from concrete practices such as CI/CD, katas, pair programming, and good branch management rather than buzzwords or theatrical facilitation.
AI-written summary · about
chapters (31)
- 0:00Welcome
- 1:12What is a Scrum Master?
- 2:59Market perception of Scrum Masters
- 5:51Motivations to be Scrum Master
- 6:53Increment vs excrement in Scrum
- 8:16Metrics and technical knowledge
- 9:20Scrum anti-patterns
- 10:29The problem with demos
- 11:11Motivation vs morale in teams
- 12:35Comfort zone and motivation
- 14:00Soft skills in Scrum
- 15:04Value of value delivery
- 16:28Empowerment and self-organization
- 18:15Team works for Scrum Master
- 18:58Silent retrospectives and bad practices
- 20:24Powerful questions and manipulation
- 21:52Nonviolent communication and psychology
- 24:42Failure culture and risks
- 25:44Minimal feedback
- 27:11Forced happiness and self-help
- 28:54Mindfulness and NLP
- 30:22Dysfunctional methods and infantilization
- 31:07Management 3.0 and perfect storm
- 32:33Questionable knowledge sources
- 33:58Certifications and agile training
- 34:39Agile events and community
- 36:25Real Scrum context
- 37:30Teams vs organizations
- 38:11Consequences of bad Scrum
- 39:17Scrum reduced to a placeholder
- 39:40Call for critical thinking
related talks
15mOne, Two, Three — You'll Be the Scrum Master!
02mInterview with
05mWhat is a Scrum Master good for?
25mDo as I Say, Not as I Do
24mIs the Scrum Master a Coach? Mentor? Facilitator? Exploring Eight Choices
45mWar is Peace, Freedom is Slavery, Ignorance is Strength, Scrum is Agile
37mWhy Scrum Fails: It’s a System Problem, Not a Team Problem
44mThe SM – Master of Balance