On page 54 of Tame Your Work Flow, you specify that Delivery Time must not be included in the Flow Time because it is not part the the Work Process and thus it is out of our span of control.
Even though I am in expert in manufacturing I tend to agree that this statement most probably applies to physical goods which need to be delivered after they have been manufactured. The Delivery process being most probably a whole different process than the manufacturing one I can understand why we do should not include it the Flow Time.
But in the domain of Knowledge Work, or more precisely for IT Delivery Teams building IT components should’nt the Delivery Process by part of the whole Software Delivery process?
With organization adopting DevOps more and more, it would then create an incentive for them to improve the delivery part of the process if this is in deed there Constraint. I have seen a lot of teams washing there hands about the Delivery process, when they actually have a lot of control on this process. It may not be 100% control, but in principle as long as they demonstrate/prove that they did there homework they should actually be in a position to deliver as soon as they are done building the solution.
In my opinion from the moment we have the Full Kit and the Flow Time meter starts and it should stop only the the solution has been delivered to the end user (i.e. deployed to production).
Thanks for sharing your thoughts on this.