Fragile development
summary
Claims Scrum is effectively a rigid cult: rules are immutable, it requires team stability that nearly never exists in software, and its daily 15‑minute timeboxed scrum plus uninterrupted Sprints back-to-back cause burnout. Presents tools and evidence: migrated project work into Tigga with GitHub integration, built an LMS (academy.esto.com), contributed open edX XBlocks and integrated with OpenStack; these concrete builds and the chosen tooling show what worked and why strict Scrum practices fail in practice.
AI-written summary · about
chapters (14)
- 0:00Intro
- 6:30Teams change
- 14:30Sprint planning
- 16:45Emergency situations
- 19:08Spiral model
- 23:03Scrum backs
- 25:00Sprints
- 32:33Tools
- 39:05Academydotcom
- 42:34Keep a prioritized backlog
- 43:47Scrum
- 45:09Story points
- 48:23Scrum for startups
- 49:51Scrum as a framework
related talks
39mWhy Scrum Is So Often 'Failed' and Criticised
34mAgile-battle
15mAdvanced Scrum techniques for optimal delivery
05mFrAgile - lessons from a failed agile transformation
26mAgile Version 2016
43mAgile Burnout
23mWhose Scrum Is It? — Scrum Development That Includes All Stakeholders, Not Just the Development Team
26mThe systemic Scrum Master