Using kanban and cfd to effectively manage agile testing

42,922 views

Published on

How can Lean/Kanban concepts help manage dev/test more effectively in an Agile environment? Excerpt from Agile Testing training by Agilesparks

Published in: Technology
0 Comments
7 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
42,922
On SlideShare
0
From Embeds
0
Number of Embeds
34,589
Actions
Shares
0
Downloads
171
Comments
0
Likes
7
Embeds 0
No embeds

No notes for slide
  • Featuer freeze – lost productivityDevelopers to testing – frsutration, inefficientLast Stories not done – finished in next sprint / left as is / thrown awayDefects Backlog increase
  • Bugs fixingStart design next iterationHelp the QA and hate Scrum 
  • Still story open with defects
  • Empty after testing, development in done testing busy  bottleneck in testingThis is a classic bottleneck in an R&D team.Testing are at their work in progress limit, meaning they cannot take on more work. Acceptance has no work in progress, what we call a “bubble”Development are at their limit as well. Nothing from Testing is DONE waiting to be pulled, which explains why Acceptance has a bubble
  • Empty after testing, development in done testing busy  bottleneck in testingThis is a classic bottleneck in an R&D team.Testing are at their work in progress limit, meaning they cannot take on more work. Acceptance has no work in progress, what we call a “bubble”Development are at their limit as well. Nothing from Testing is DONE waiting to be pulled, which explains why Acceptance has a bubble
  • Empty after testing, development in done testing busy  bottleneck in testingThis is a classic bottleneck in an R&D team.Testing are at their work in progress limit, meaning they cannot take on more work. Acceptance has no work in progress, what we call a “bubble”Development are at their limit as well. Nothing from Testing is DONE waiting to be pulled, which explains why Acceptance has a bubble
  • Automation – not just test automation!How can we help you spend more time actually testing (compared to setup, and other wastes) (http://theoryofconstraints.blogspot.com/2007/06/toc-stories-2-blue-light-creating.html) How often do we need to retest? Why?ATDD - drives better code into testing, as well as offload some testing workAgree on “READY for Testing” criteria for stories, setup relevant team rules and processes.
  • Low quality no bottleneck as development and testing busy Bottleneck in analysis as development busy with low qualiy
  • Using kanban and cfd to effectively manage agile testing

    1. 1. Lean in Agile Testing<br />Using Kanban and Cumulative Flow to effectively manage Agile Testing<br />Yuval Yeret<br />development<br />testing<br />effort<br />end of cycle<br />time<br />Copyright notice<br />These slides are licensed under Creative Commons.Feel free to use these slides & pictures as you wish, as long as you leave my name and the Agilesparks logo somewhere. /<br />
    2. 2. Throughout a traditional project/release, workload is usually unbalanced, creating severe bottlenecks<br />development<br />testing<br />effort<br />end of cycle<br />time<br />
    3. 3. Let’s start with a classic burndown/burnup chart<br />
    4. 4. So we want to get to this…<br />
    5. 5. 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 />
    6. 6. How do we Visualize the work status in more depth?<br />TODO<br />Work in Process (WIP)<br />Done<br />
    7. 7. The Cumulative Flow Diagram<br />Introduced in Lean Product Development by Don Reinertsen and David Anderson<br />Visualize where the Features/Stories are in the workflow across time<br />TODO<br />Work in Process (WIP)<br />Done<br />
    8. 8. Mushon<br />Inbar<br />Inbar<br />Elad<br />Mushon<br />Elad<br />Inbar<br />Elad<br />Mushon<br />How to do a CFD<br />
    9. 9. How to do a CFD<br />
    10. 10. What you see on a CFD<br />Total Scope<br />Work in Process (WIP)<br />Average Cycle Time<br />TODO<br />Burnup<br />Done<br />
    11. 11. Elaborating the WIP<br />Heavy load on QA<br />TODO<br />Dev<br />Heavy load on Dev<br />Test<br />Done<br />
    12. 12. Discussion – What do you see happening in your teams?<br />Are all stories finished each Sprint?<br />How are the teams achieving that? <br />What happens to those stories that are not finished?<br />How does the open defects count look during the release? <br />
    13. 13. Lets Sprint!<br />This is the Kanban Story Board for a Scrum Sprint<br />First – lets see how it looks without any focus on Flow<br />
    14. 14. First day - starting many stories at once - each to his own<br />
    15. 15. Day 4<br />after a few days, a story is finally ready for testing...<br />
    16. 16.
    17. 17.
    18. 18.
    19. 19. Day 6<br />What do you think so far?<br />
    20. 20. Day 8<br />
    21. 21. Board at Sprint Review Time<br />What’s this? <br />Why?<br />
    22. 22. Next Sprint – Day 1<br />Starting with Leftovers<br />Note: Harder to plan around those btw...<br />
    23. 23. “Scrumfall” in CFD<br />Total Scope<br />Work in Process (WIP)<br />Average Cycle Time<br />TODO<br />Burnup<br />Done<br />
    24. 24. If we use a WIP Limit...<br />TODO<br />Test<br />Dev<br />Average Cycle Time<br />Work in Process (WIP)<br />Done<br />
    25. 25. Pop Quiz<br />Blocked/Impeded Card<br />What does this mean?<br />Full story at http://yuvalyeret.com/2010/08/03/finding-the-right-dev-to-test-ratio-when-working-in-kanban/<br />
    26. 26. Pop Quiz<br />Empty downstream (Bubble)<br />Dev Done almost Full<br />A lot of WIP in Test<br />Empty Test Done<br />Test Bottleneck!<br />Full story at http://yuvalyeret.com/2010/08/03/finding-the-right-dev-to-test-ratio-when-working-in-kanban/<br />
    27. 27. Dealing with bottlenecks – tactical level<br />Fix open defects on our Stories<br />3<br />WIP Limit!<br />Can’t start new DEV work!<br />Help us with Blocker<br />T<br />D<br />T<br />T<br />D<br />D<br />Help us automate tests for this story<br />How can I help current stories?<br />
    28. 28. Dealing with bottlenecks – strategic view<br />Automate Setups and Test Data<br />Half of our work is not core test work. Maybe you can take some of it, or help us reduce waste there <br />Improve Dev Done quality! – less retesting for us<br />3<br />T<br />D<br />Creating more Blue Light - TOC<br />T<br />D<br />Help us do ATDD so you can develop based on our test expectations, and also offload some automation effort from us<br />T<br />Come pair with us, you’ll probably see things from our perspective and have some ideas how to help!<br />D<br />How can I help you be more efficient?<br />
    29. 29. What happens if DONE DONE is a lot of work?<br />Examples:<br />Non-functional Testing<br />E2E Testing<br />I18N/L10N/Documentation<br />Test Automation<br />Alternatives<br />Make the sprint longer to include them – BAD<br />Don’t include them – how to manage them then?<br />
    30. 30. Flowing all the way to DONE DONE<br />DONE DONE<br />READY<br />DONE<br />
    31. 31. Example Policy - Classes of Service for Downstream Involvement<br />Red – Must be involved hands on<br />Yellow – Advise/Consult, but most work in Teams<br />Green – don’t need any involvement<br />Why? To get best results with available resources<br />
    32. 32. Pop Quiz<br />What do you think is happening here?<br />Do we have a bottleneck ? <br />
    33. 33. Build Quality In<br />
    34. 34. Jidoka – Stop the line<br />Don’t let defects accumulate and hurt you later<br />Keep the open defects count LOW<br />
    35. 35. Summary<br />Limit work in process:<br />Stop starting, start finishing<br />
    36. 36. Want to learn more?<br />Lean-flavored Agile Testing Training by Agilesparks<br />http://www.agilesparks.com/files/AgileTestingAS.pdf<br />Kanban training by Agilesparks<br />http://www.agilesparks.com/files/KanbanforManagers.pdf<br />Contact us at info@agilesparks.com for more information<br />

    ×