Playing Games with Scrum!
summary
Claim: many developers dislike Scrum because teams play games with its rules; a tiny tweak like the Monopoly “free parking” house rule breaks game dynamics, and a homemade board game built by two kids fails on the first move because of untested design. Scrum has ~25 years of play‑testing; apply the Nigel scale: level 1 core rules (don’t bend), level 2 local practices (coach & adapt), level 3 anti‑agile (cut). Build the environment like a dungeon master, play‑test processes, prefer the simplest rules that enable rich, repeatable outcomes.
AI-written summary · about
chapters (13)
- 0:00Welcome to Playing Games with Scrum
- 2:30Developers hate Scrum debate
- 10:15Playing games with Scrum
- 14:09Rule tweaks consequences
- 19:03Rolling your own agile dangers
- 26:08Games and process complexity
- 31:50Scrum Master as Dungeon Master
- 35:43Scrum cheating and malpractice
- 37:50Scrum play-tested 25 years
- 41:22Nigel Scale for Scrum
- 44:12Scrum practices evaluation
- 47:22Scrum misconceptions and abuses
- 49:06Playing Scrum with joy
related talks
01h 00mFish Bowl
37mWhy Scrum Fails: It’s a System Problem, Not a Team Problem
41mYour Scrum Master Is Deceiving You... and You Know It!
49mHow Agile broke peace in steady Casino Business
34mAgile-battle
45mWar is Peace, Freedom is Slavery, Ignorance is Strength, Scrum is Agile
51mDon't Kill Agility with Agile Processes
15mAdvanced Scrum techniques for optimal delivery