The Lineage to Scrum in the Modern History of Software Development — Knowing the 'Why' Builds Confidence
summary
A historical timeline connects artifacts—a 1990 company video, cited papers from the 1968 software crisis through 1976 and 1989, and the Agile Samurai book—to show how recurring failures from the waterfall “no-return” myth led to iterative methods and Extreme Programming as practical fixes. Data from booth responses and Findy TeamPlus metrics are used to populate the timeline, and the argument is that making veterans’ tacit lessons explicit gives novices usable decision axes so they develop judgment rather than blind obedience.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 3:09Why this talk
- 9:24Waterfall in the 1980s
- 13:46Waterfall myth origins
- 15:55Military Waterfall failures
- 17:18Agile and Scrum birth
- 18:43Agile Samurai truths
- 19:52Call to practice Agile
related talks
03mThe origins of Agile
36mWhat Your Mother Never Told You About Agile Development
26mIs Agile still the answer?
26mAgile Version 2016
41mWar is Peace, Freedom is Slavery, Ignorance is Strength, Scrum is Agile
50mThe 7 Habits of Highly Successful Samurai, and How That Helps Rubyists
01h 13mScrum for Executives, Leaders, and Your Boss
30mA Test Team's Unexpected Journey from Waterfall to Agile