A quick tour of delivery management (and why it matters)
summary
Four concrete moves decide whether to watch: a four-step recipe that actually names actions — build an accurate plan that answers five questions (outcome, scope, estimate, critical dependencies, success criteria) and gives a range (example: “Jan 26 ± one month”); show visible progress weekly or daily with a walking skeleton and demos; anticipate risk with premortems and contingency buffers; and drive decisions via steering committees. Measure with lead time and deployment frequency, change failure rate and MTTR, and % time on new capabilities to prove it works.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 0:35Pats background
- 1:14What keeps you up at night
- 1:47What people say
- 2:47Trust
- 4:12Dependencies
- 5:45What does delivery mean
- 13:18Build an accurate plan
- 16:55Precisely inaccurate
- 19:55User story mapping
- 22:34Contingency
- 24:27Decision making
related talks
22m4 Maps of DevOps
31mA Successful DevOps Initiative Starts with Knowing Your Numbers
31mScaling delivery management for 50 teams
22mPanel Discussion: Let's Improve - Leverage DORA to Im...
41mContinuous delivery in 10 easy mistakes
06mDelivery Metrics: the good, the bad, and the totally ridiculous
20mKeynote: The Four Keys: Measuring Software Delivery
24mBringing Product Thinking into DevOps