Dual Value Streams conceal transaction and opportunity costs
The goal of Continuous Delivery is to optimise cycle time in order to increase product revenues, and cycle time is measured as the average lead time of the value stream from code checkin to production release. This was memorably summarised by Mary and Tom Poppendieck as the Poppendieck Question:
“How long...Read More »
Continuous Delivery and DevOps experience reports from the wild
I am excited to announce you can now buy Build Quality In by Matthew Skelton and I on Leanpub!
Build Quality In is an anthology of first-person narratives from Continuous Delivery and DevOps practitioners. We have an incredible group of contributors, with...Read More »
Separate out analysis to preserve commit stage processing time
The entry point of a Continuous Delivery pipeline is its Commit Stage, and as such manages the compilation, unit testing, analysis, and packaging of source code whenever a change is committed to version control. As the commit stage is responsible for identifying defective code it represents a...Read More »
Trunk Based Development supports Optimistic and Pessimistic Release Branching
Trunk Based Development is a style of software development in which all developers commit their changes to a single shared trunk in source control, and every commit yields a production-ready build. It is a prerequisite for Continuous Delivery...Read More »
Older Entries »
Upcoming talks on Continuous Delivery
I will be talking about “Release Testing Is Risk Management Theatre” at the following events:
Hope to see you at one of the above!
...Read More »