7 habits of a high performing team
summary
Claims concrete habits: work in small steps — ~1–2 hour steps so a six‑person paired team can ship ~12 steps/day; deploy every change — one change equals one deploy, ideally auto‑on‑merge and single‑click; separate deploy from release with feature flags (larable pennant, launch darkley, post hog). Testing spans unit tests to production synthetics and chaos engineering. Pair programming costs ~15% time but cuts defects and speeds onboarding. DORA numbers: ~209× more deployments, 106× faster lead time, 7× lower failure rate, 264× faster recovery.
AI-written summary · about
chapters (18)
- 0:00Team performance
- 2:19Work small steps
- 5:06Interruptibility
- 6:17Steerability
- 8:17Motivation
- 9:14Known bugs
- 11:27Deploy changes
- 13:56Separate deploy
- 16:28Testing workflow
- 18:43Production testing
- 19:47Validate ideas
- 22:24Repository pattern
- 25:55Simplicity
- 26:20Pair programming
- 29:01Learning culture
- 30:44Stakeholder value
- 32:11Performance stats
- 33:01Virtuous cycles
related talks
44mEnhancing the Performance of Engineering Teams
38mBuilding a high quality product
52mSecrets of High Performing Teams: Science Edition
44mI Deploy On Fridays
38mJust Ship It!
30m10 Ways to Improve How You Ship Software
41mContinuous delivery in 10 easy mistakes
58mKeynote: Seven Habits of a (Mostly) Successful Team