Fish Bowl
summary
Argument that Scrum is old fashioned and often performed as checklists not mindset, with concrete consequences: rigid product owner roles creating single‑point decisions, mandated 70% code coverage producing useless tests, and teams finishing Sprints without testing or refactoring. Evidence cited: Nokia adoption then collapse, empirical work showing fewer defects with pair programming studies (Lori Williams, JP Morgan), alternatives used are Kanban, continuous delivery and Lean Startup to focus on outcomes rather than ceremonies. Continuous automation and rotating pairs are practical fixes.
AI-written summary · about
chapters (21)
- 0:00Scrum outdated framework
- 3:16Agile versus being agile
- 6:51Scrum in early maturity
- 9:20Balance problem with Scrum
- 12:10Process culture hurts agility
- 13:54Nokia’s Scrum debate
- 17:20Scrum certification impact
- 20:57Beyond Scrum to modern agile
- 23:43Flawed product owner role
- 26:10Outcomes over deliverables
- 27:53Modern bottlenecks in delivery
- 31:49Revisiting Agile Manifesto
- 34:40Scientific methods in teams
- 37:55Pair programming evidence
- 43:10Pair programming benefits
- 45:59Pair programming context
- 47:03Code review evolution
- 50:17Breaking tester-developer silos
- 53:30Genius versus teamwork
- 56:18Knowledge silos and dynamics
- 59:11Q&A
related talks
51mDon't Kill Agility with Agile Processes
34mAgile-battle
16mScrum Buts - and how to remove them
24mWhatever Works – Scrum, Kanban, or Nothing?
37mWhy Scrum Fails: It’s a System Problem, Not a Team Problem
01h 13mScrum for Executives, Leaders, and Your Boss
45m#NoFrameworks: Build Your Own Agile, Burn the Playbook
42mWhat your mother never told you about agile development