a whiteboard, break down the flow of work from the moment you start it to when it's finished from the moment you start it to when it's finished into into distinctive steps distinctive steps and and draw a column for each draw a column for each
And put them on the whiteboard. Each task will move from left to right until it's done and leaves the workflow. from left to right until it's done and leaves the workflow.
so start with your best guess and fine-tune over time. so start with your best guess and fine-tune over time. The ultimate goal is to achieve The ultimate goal is to achieve constant, high throughput and personal / team performance. constant, high throughput and personal / team performance. After you introduce the WIP limits you can try to After you introduce the WIP limits you can try to propagate them back through the workflow, propagate them back through the workflow, observe results and adapt. observe results and adapt.
day, for each column, mark how many tasks are in it or somewhere further down the workflow. are in it or somewhere further down the workflow. This will produce a mountain-like looking chart, which gives insight into This will produce a mountain-like looking chart, which gives insight into the process, shows past performance and allows to predict future results the process, shows past performance and allows to predict future results
is the One of the many things you can read from it is the mean time for task to get through the workflow mean time for task to get through the workflow Note that without limit on Work In Progress, Note that without limit on Work In Progress, the Mean Cycle Time tends to increase drastically ... the Mean Cycle Time tends to increase drastically ... www.slideshare.net/yyeret/explaining-cumulative-flow-diagrams-cfd
• perfect for distributed teams • real time collaboration • accessible from everywhere • provides in-depth analytics, including Cumulative Flow • retains data about your past performance http://kanbantool.com