Managing Releases by the Numbers (Really?)
summary
Argues that numeric release gates often mislead: organizations enforce no P0/P1 bugs allowed or “lockdown 28 days before release” and still ship catastrophic failures (healthcare.gov, national census rollouts, state benefits system). Proposes replacing blind metrics with structured cross-team conversations and lightweight integration checks: daily standups plus cross-team leads over coffee, ad hoc integration testing, and remote calls (Skype/Hangouts/GotoMeeting). Cites a Science paper showing conversation changes decisions, so use story-driven risk discussions and talk to each other.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 8:02What does this mean
- 9:51Obamacare
- 12:36What do these hard facts tell us
- 18:41Talk to each other
- 26:05Durably Reducing Transphobia
- 28:13NonEmotional Facts
- 29:39Lord Kelvin
- 32:13Conversation
- 33:09Wrap up
related talks
18mManaging Change
05mRadical Transparency for Software Teams
49mChanging Testing Culture in a Ginormous Company
22mFail Fast, Fail Often - Make Safety a Prerequisite for your Team
09m"Why and how not to be a gatekeeper"
20mInfluencing through getting your carrots in a row
29mOvercoming bureaucracy to succeed at digital transformation
52mThe Developer Rhapsody