Striving for engineering excellence: Data-informed organization
summary
Flow Health treats engineering as a service to product and measures it: cycle time per team has a one‑day north star and falls from about five days to an average of 2 days 9 hours after process changes. Teams run a quarterly tech quota governed by error budget / SLO (crash‑free sessions) and use SonarQube, churn vs complexity charts and unit‑coverage scoring to pick hot spots. A Kinesis→Kafka migration runs dual implementations to reduce risk; smaller vertical stories and API‑first work shorten lead time.
AI-written summary · about
chapters (11)
- 0:00Introduction and speakers
- 1:28What is engineering excellence
- 8:08Why engineering excellence matters
- 13:03Measuring cycle time
- 16:14Technical improvements and refactoring
- 20:14Error budget and SLOs
- 22:00Charm versus complexity graph
- 26:14Key takeaways and summary
- 27:18Q&A session
- 42:09Online audience Q&A
- 47:50Closing and booth invitation
related talks
47mMap and Measure your way to Performance
44mEnhancing the Performance of Engineering Teams
31mImproving engineering effectiveness: A journey for the entire organization
51mImproving Software Flow
28mMeasuring Success
15mOptimizing the engineering value stream
06mRemoving engineering friction: Creating an evolutionary culture
34mAn Engineering Team Where Everyone is a Leader