Understanding Project Performance usingCumulative Flow Diagrams<br />Yuval Yeret<br />Agile Coach @ Agilesparks<br />yuval...
Brief Intro<br />AgileSparks is an elite team focused entirely on helping companies improve their product development oper...
Lets start with a classic burndown/burnup chart<br />
Lets start with a classic burndown/burnup chart<br />What’s wrong here?<br />
Lets start with a classic burndown/burnup chart<br />What’s wrong here?<br />Working software only towards the end of the ...
Lets start with a classic burndown/burnup chart<br />What’s wrong here?<br />Working software only towards the end of the ...
Lets start with a classic burndown/burnup chart<br />What’s wrong here?<br />Working software only towards the end of the ...
So we want to get to this…<br />
So we want to get to this…<br />So what’s the difference?<br />
So we want to get to this…<br />So what’s the difference?<br />Notice how the done work is spread more evenly<br />
So we want to get to this…<br />So what’s the difference?<br />Notice how the done work is spread more evenly<br />This re...
So we want to get to this…<br />So what’s the difference?<br />Notice how the done work is spread more evenly<br />This re...
Keys to steady burnup<br />Effectively sized and testable stories<br />Allow finishing work end to end quickly<br />Focus ...
How to make this happen?<br />Get the Product Owner to provide INVEST stories<br />Provide more visibility to WHERE work i...
How do we Visualize the work status in more depth?<br />
How do we Visualize the work status in more depth?<br />Wow!<br />What’s that?<br />This is called Cumulative Flow Diagram...
How do we Visualize the work status in more depth?<br />
Mushon<br />Inbar<br />Inbar<br />Elad<br />Elad<br />Mushon<br />Inbar<br />Mushon<br />Elad<br />
So a cumulative flow is built of snapshots of the board summary per day<br />
And provides a LOT of data<br />WIP<br />Mean Cycle Time<br />
Now, how can we get more details?<br />Lets dive into the workflow<br />
Wide means lots of WIP<br />Means problems finishing work<br />OR<br />Next stage cannot deal with work now <br />
http://agileanalysis.blogspot.com/2008/12/finger-charts.html<br />
This is better!<br />
What is this?<br />
So what do we need for a CFD?<br />Have a defined workflow, even a simple one (TODO, IN PROGRESS, DONE) <br />Track state ...
Why use CFD?<br />One visibility report provides insight to Burnup, Cycle Time, WIP, Bottlenecks<br />Drives Continuous Im...
The visibility partner of Kanban<br />Replaces Burnup/Burndown for Kanban teams/groups. <br />
Lets revisit KanbanLand…<br />HenrikKniberg came up with “One day in Kanban Land” – a comic explaining the key Kanban conc...
35<br />
36<br />
37<br />
Upcoming SlideShare
Loading in...5
×

Explaining Cumulative Flow Diagrams - CFD

41,936

Published on

Cumulative Flow Diagrams (CFDs) are used in Lean/Kanban and help trend WIP, Cycle Time, Throughput in projects or flow-based teams/groups.
Learn how to read a CFD and how to use them.

Published in: Technology
6 Comments
73 Likes
Statistics
Notes
No Downloads
Views
Total Views
41,936
On Slideshare
0
From Embeds
0
Number of Embeds
18
Actions
Shares
0
Downloads
1,194
Comments
6
Likes
73
Embeds 0
No embeds

No notes for slide

Transcript of "Explaining Cumulative Flow Diagrams - CFD"

  1. 1. Understanding Project Performance usingCumulative Flow Diagrams<br />Yuval Yeret<br />Agile Coach @ Agilesparks<br />yuval@agilesparks.com<br />Mobile: 054-4802458<br />
  2. 2. Brief Intro<br />AgileSparks is an elite team focused entirely on helping companies improve their product development operations, by leveraging Lean/Agile/Scrum thinking and techniques. <br />Yuval Yeret – Lean/Agile Consultant/Coach, coming from R&D leadership background, specializing in scaling agile through Lean. Find more about me at http://www.linkedin.com/in/yuvalyeret, my google profile<br />
  3. 3. Lets start with a classic burndown/burnup chart<br />
  4. 4. Lets start with a classic burndown/burnup chart<br />What’s wrong here?<br />
  5. 5. Lets start with a classic burndown/burnup chart<br />What’s wrong here?<br />Working software only towards the end of the iteration/project<br />
  6. 6. Lets start with a classic burndown/burnup chart<br />What’s wrong here?<br />Working software only towards the end of the iteration/project<br />So?<br />
  7. 7. Lets start with a classic burndown/burnup chart<br />What’s wrong here?<br />Working software only towards the end of the iteration/project<br />So?<br />Risk of missing the iteration…<br />Work is not spread evenly, bottlenecks<br />We call it “Scrumfall”<br />
  8. 8. So we want to get to this…<br />
  9. 9. So we want to get to this…<br />So what’s the difference?<br />
  10. 10. So we want to get to this…<br />So what’s the difference?<br />Notice how the done work is spread more evenly<br />
  11. 11. So we want to get to this…<br />So what’s the difference?<br />Notice how the done work is spread more evenly<br />This reduces risk due to leftovers,<br />Much more effective and sustainable load for everyone, <br />And allowing shorter sprints if needed<br />
  12. 12. So we want to get to this…<br />So what’s the difference?<br />Notice how the done work is spread more evenly<br />This reduces risk due to leftovers,<br />Much more effective and sustainable load for everyone, <br />And allowing shorter sprints if needed<br />Great<br />How do I do it?<br />
  13. 13. Keys to steady burnup<br />Effectively sized and testable stories<br />Allow finishing work end to end quickly<br />Focus on few stories at a time, rather than work on too much at once<br />
  14. 14. How to make this happen?<br />Get the Product Owner to provide INVEST stories<br />Provide more visibility to WHERE work is before its DONE<br />Manage the work in progress to drive focus<br />
  15. 15. How do we Visualize the work status in more depth?<br />
  16. 16. How do we Visualize the work status in more depth?<br />Wow!<br />What’s that?<br />This is called Cumulative Flow Diagrams<br />Introduced by Lean Thought Leaders Don Reinertsen  and David Anderson<br />The idea is to visualize where the features/stories are in the workflow across time<br />
  17. 17. How do we Visualize the work status in more depth?<br />
  18. 18. Mushon<br />Inbar<br />Inbar<br />Elad<br />Elad<br />Mushon<br />Inbar<br />Mushon<br />Elad<br />
  19. 19.
  20. 20.
  21. 21.
  22. 22.
  23. 23.
  24. 24. So a cumulative flow is built of snapshots of the board summary per day<br />
  25. 25. And provides a LOT of data<br />WIP<br />Mean Cycle Time<br />
  26. 26. Now, how can we get more details?<br />Lets dive into the workflow<br />
  27. 27. Wide means lots of WIP<br />Means problems finishing work<br />OR<br />Next stage cannot deal with work now <br />
  28. 28. http://agileanalysis.blogspot.com/2008/12/finger-charts.html<br />
  29. 29. This is better!<br />
  30. 30. What is this?<br />
  31. 31. So what do we need for a CFD?<br />Have a defined workflow, even a simple one (TODO, IN PROGRESS, DONE) <br />Track state of Features/Stories/Requirements , including historical data<br />Cumulative Flow can be easily generated based on this<br />Can be improved to be based on Size of items e.g. Story/Feature Points. <br />When using this, can mix different entities on same CFD<br />With # of items, items need to be of same kind (e.g. stories/epics but not a mix)<br />
  32. 32. Why use CFD?<br />One visibility report provides insight to Burnup, Cycle Time, WIP, Bottlenecks<br />Drives Continuous Improvement, great companion to discussions about limiting/managing work in progress (WIP). <br />Can be applied for<br />Scrum Teams<br />End to end product development project/group<br />Any kind of team chewing customer-valued work items <br />
  33. 33. The visibility partner of Kanban<br />Replaces Burnup/Burndown for Kanban teams/groups. <br />
  34. 34. Lets revisit KanbanLand…<br />HenrikKniberg came up with “One day in Kanban Land” – a comic explaining the key Kanban concepts. <br />Lets try to see how a Cumulative Flow Diagram looks for each of the hours in Kanban Land…<br />Comic courtesy and copyright HenrikKniberg, Crisp SE<br />
  35. 35. 35<br />
  36. 36. 36<br />
  37. 37. 37<br />
  38. 38. 38<br />
  39. 39. 39<br />
  40. 40. 40<br />
  41. 41. 41<br />
  42. 42. 42<br />
  43. 43. 43<br />
  44. 44. 44<br />
  45. 45. 45<br />
  46. 46. 46<br />
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×