Collective Risk Management
summary
Claims that collective risk management works get demonstrated with concrete outcomes: a developer team ships a spreadsheet workaround that takes four hours to build and becomes an immediate hit after adding analytics, a codebase with a 28-page function forces a six to eight month stability overhaul that stops crashes, an experimental feature from a summer intern scales into hundreds of millions in revenue, and techniques like chartering, risk lists, tests, pair programming, continuous integration and Monte Carlo simulations are used to surface and derisk uncertainty.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 3:18Product owner role
- 7:10Psychological safety
- 10:22Risk aversion lessons
- 12:07Extreme Programming risks
- 15:23Code ownership inspiration
- 16:48Risk vs reckless management
- 21:50Sufficient design
- 24:20Software quality visualization
- 28:11Chartering and risk lists
- 31:00Lean Startup risks
- 32:45Modern Agile principles
- 33:47Whole-team collaboration
- 36:59Product trios mentality
- 38:02Empowering innovation
- 39:47Supporting practices
related talks
11mManaging business risks together
07mIf Development is a Game, How Do I Win?
35mWhy Risk Management Requires Taking Risks: A Practical Guide...
40mSix Years in Review: Transforming Company Culture to Embrace Risk
21mRadical Therapy for Software Teams
49mThe real secret to high-performing teams
32mNavigating Uncertainty: Operational Risk Management in the Open-Source Sector
41mAbout Pink Elephants, Giant Giraffes