Continuous Huddling is a software delivery practice where the members of a team huddle frequently. This practice encompasses analyzing, guiding the development, validating and communicating about the work requirements with the right people at the right time. Teams...
Author
Paulo Caroli

More from Paulo Caroli
Blog Posts
Stable System, WIP limit and Pull System
On myprevious blog post, I wrote that WIP limit and Pull system are the guiding rules that make a system stable. I decided to make a visual representation for Stable System, and explore the what-if conditions for WIP limit and Pull System. ...
Little’s law and stable systems
Little’s law is defined in terms of stable systems. On my previous post, I have described my bar as a stable system: “Whenever a bottle finishes, I remove it from the bar. Then I open a new one, and add it to the bar. My bar is a stable system: the rate at which...
Lead time: Applying Little’s Law to track it
“The average number of work items in a stable system is equal to their average completion rate, multiplied by their average time in the system.” ~ John Little, 1961 The text above is from "A Proof for the Queuing Formula" by Little, J. D. C. (1961). It is knows...
Lead Time – three extremely simple ways to manually track it
Lead time—the time elapsed from the work start to completion-- is important and is a key performance indicator (KPI) that every Agile team should track. Poor lead time causes bottlenecks in the team production flow, inefficiencies, delay costs, not to mention unhappy...
Continuous Delivery: lead time and cycle time
I have seen quite a few people mixing up these terms: lead time and cycle time. I am not sure about the reason for the confusion. I think Continuous Delivery provides a great example for explaining each one of these important parameters: lead time and cycle...







