It's impossible to have small batches and thus Continuous Delivery if there's a part of the (tech) value stream that has high transaction cost.
At this place in the system batch size starts to build up and clogs downstream part.
Like an elephant moving through a boa constrictor.
At this place in the system batch size starts to build up and clogs downstream part.
Like an elephant moving through a boa constrictor.
Conversely, looking for the place in the system where there's the highest transaction cost, is a great leverage point in order to increase the throughput of the whole system.
Yup, you got it, #tocot way of continuous improvement.
Yup, you got it, #tocot way of continuous improvement.
Also, for a long time, I was thinking that minimizing transaction cost is THE thing that enables batch size reduction.
But just recently had the epiphany that it's necessary, but not sufficient.
But just recently had the epiphany that it's necessary, but not sufficient.
What compliments it and creates both necessary and sufficient conditions is increasing the cost of (keeping) the inventory.
I think of this analogy as a ball that's on a flat surface and has an obstacle in front of it.
Obstacle is the high transaction cost and flat surface is the low cost of keeping the inventory.
Minimizing the transaction cost is removing the obstacle.
Obstacle is the high transaction cost and flat surface is the low cost of keeping the inventory.
Minimizing the transaction cost is removing the obstacle.
This is necessary, but not sufficient condition for the ball to start rolling.
We need to address the inertia by tilting the ground which equals to increasing the cost of keeping inventory and then the ball starts rolling downhill (a small batch moving fast through the system).
We need to address the inertia by tilting the ground which equals to increasing the cost of keeping inventory and then the ball starts rolling downhill (a small batch moving fast through the system).
TCR from @KentBeck is a great example of applying 'increase cost of (keeping) the inventory' idea in order to incentivize batch size reduction.
Another example: 'deleting a branch if it becomes older than a day'. A bit extreme yeah, but this serves as an enabling constraint.
Another example: 'deleting a branch if it becomes older than a day'. A bit extreme yeah, but this serves as an enabling constraint.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
