CI/CD is just the Beginning: Optimize Value Creation with Flow Framework
summary
Claim: measure and fix end-to-end software delivery using the Flow Framework by classifying every artifact as a feature defect risk or debt and mapping tools like JAMA JIRA ALM ServiceNow TFS and Salesforce into three models product activity and integration. Concrete findings include a 120 day idea‑to‑delivery where development is only 2.5% of time and 90 day code waits a 10% time savings from removing one approval and chaotic boards with 55 states per item. Core metrics are flow velocity, flow efficiency, flow time, flow load and flow distribution.
AI-written summary · about
chapters (6)
- 0:00Introduction and context
- 2:30Real-world bottleneck stories
- 9:22Introducing the flow framework
- 13:03The flow metrics
- 18:55Modeling for successful metrics
- 30:44Summary and next steps
related talks
47mMap and Measure your way to Performance
29mFlow Engineering - boost velocity, quality & happiness
48mStrong Foundations: Insightful learning vs trial-and-error in CI/CD
24mCI/CD Best Practices to Deliver Software Faster
41mContinuous Delivery Transformation: The New Way of Working
17mCI/CD - Build/Deploy Automation
31mThe Continuous Delivery Paradox - Balancing Business Value with Speed
30mThe Case for Value Stream Architecture