My goal here is not to cover all those patterns again, which mainly are still a work in progress, but to share a specific story about measuring flow.In 2010-2011, I was in charge of a software development team located in Paris and Mumbai.They were not focusing on their lead time, they used a tasks management tool focusing on who is responsible for what and managing queues without limit or flow measurements.We were also not satisfied with the way we all were working and coordinating our clients.Contact Open Minded Singles in Your Area and Establish Connections with Good Looking Transgender Singles Ready to Have a Date!Find a Lasting Relationship, a Casual Partner or a New Friend in Our Club!We experienced most of the behavioral changes listed above and our cycle time was reducing.
During 2012 the Kanban Leadership Retreat in Austria Mayrhofen, Pawel Brodzinski hosted an open space session dedicated to behavioural changes. As Pawel explains in his blog post, we shared stories about emerging patterns from our Kanban experiences.
We had several activities on our hands: business analysis, development, test and functional support.
We were using the Kanban method to guide our collective work and our work improvement.
Thus one day we decided to automatically measure their Cumulative Flow Diagram (CFD) and make it visible.
The average lead time was around 10 days for one very simple request.
At the beginning they were ignoring measures, just looking at odd graphs.