Evolution From #Noprojects to Continuous Digital
summary
Claim: projects are a 1970s hangover and must be replaced by continuous digital practices that fund teams not temporary scopes. Cites Domino’s app as the revenue engine, John Deere spending $260M/year, Raspberry Pi at $35 vs mainframe rent $1.75M/month to show changed economics. Recommends minimally viable team (2–3 people), continuous delivery, small batches, venture-capital style tranches for funding, amoeba-style units, and measuring teams by business impact rather than schedule or features.
AI-written summary · about
chapters (17)
- 0:00Intro
- 1:04Projects are evil
- 4:12Projects dont work
- 10:35Economies of scale
- 21:03Innovation and processes
- 24:57Project model hangover
- 27:58A model for continuous business
- 30:15Stable teams
- 31:53The bottom line
- 32:45Teams
- 34:33Mission
- 35:53Skills
- 37:12Organizational Design
- 38:40Minimal Viable Team
- 41:36Start Small Grow
- 42:16Split the Team
- 46:42Money and Governance
related talks
53m#NoProjects Beyond Projects - Why Projects Are Wrong & What To Do Instead
30mAn Evolutionary Approach to DevOps
54mGetting Unstuck. Strategies for Surviving in a Rapidly Changing Post-Agile World
01h 00mBeyond the innovator’s dilemma
24mEvolution of Continuous Product Discovery
53mKeynote: Value Driven Development - Maximum Impact, Maximum Speed
31mThe Continuous Culture
01h 02mSurviving the Innovators Dilemma