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

1. Lean in Agile Testing Using Kanban and Cumulative Flow to effectively manage Agile Testing Yuval Yeret development testing effort end of cycle time Copyright notice 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. /

2. Throughout a traditional project/release, workload is usually unbalanced, creating severe bottlenecks development testing effort end of cycle time

3. Let’s start with a classic burndown/burnup chart

4. So we want to get to this…

5. Keys to steady burnup Effectively sized and testable stories Allow finishing work end to end quickly Focus on few stories at a time, rather than work on too much at once

6. How do we Visualize the work status in more depth? TODO Work in Process (WIP) Done

7. The Cumulative Flow Diagram Introduced in Lean Product Development by Don Reinertsen and David Anderson Visualize where the Features/Stories are in the workflow across time TODO Work in Process (WIP) Done

8. Mushon Inbar Inbar Elad Mushon Elad Inbar Elad Mushon How to do a CFD

9. How to do a CFD

10. What you see on a CFD Total Scope Work in Process (WIP) Average Cycle Time TODO Burnup Done

11. Elaborating the WIP Heavy load on QA TODO Dev Heavy load on Dev Test Done

12. Discussion – What do you see happening in your teams? Are all stories finished each Sprint? How are the teams achieving that? What happens to those stories that are not finished? How does the open defects count look during the release?

13. Lets Sprint! This is the Kanban Story Board for a Scrum Sprint First – lets see how it looks without any focus on Flow

14. First day - starting many stories at once - each to his own

15. Day 4 after a few days, a story is finally ready for testing...

19. Day 6 What do you think so far?

20. Day 8

21. Board at Sprint Review Time What’s this? Why?

22. Next Sprint – Day 1 Starting with Leftovers Note: Harder to plan around those btw...

23. “Scrumfall” in CFD Total Scope Work in Process (WIP) Average Cycle Time TODO Burnup Done

24. If we use a WIP Limit... TODO Test Dev Average Cycle Time Work in Process (WIP) Done

25. Pop Quiz Blocked/Impeded Card What does this mean? Full story at http://yuvalyeret.com/2010/08/03/finding-the-right-dev-to-test-ratio-when-working-in-kanban/

26. Pop Quiz Empty downstream (Bubble) Dev Done almost Full A lot of WIP in Test Empty Test Done Test Bottleneck! Full story at http://yuvalyeret.com/2010/08/03/finding-the-right-dev-to-test-ratio-when-working-in-kanban/

27. Dealing with bottlenecks – tactical level Fix open defects on our Stories 3 WIP Limit! Can’t start new DEV work! Help us with Blocker T D T T D D Help us automate tests for this story How can I help current stories?

28. Dealing with bottlenecks – strategic view Automate Setups and Test Data Half of our work is not core test work. Maybe you can take some of it, or help us reduce waste there Improve Dev Done quality! – less retesting for us 3 T D Creating more Blue Light - TOC T D Help us do ATDD so you can develop based on our test expectations, and also offload some automation effort from us T Come pair with us, you’ll probably see things from our perspective and have some ideas how to help! D How can I help you be more efficient?

29. What happens if DONE DONE is a lot of work? Examples: Non-functional Testing E2E Testing I18N/L10N/Documentation Test Automation Alternatives Make the sprint longer to include them – BAD Don’t include them – how to manage them then?

30. Flowing all the way to DONE DONE DONE DONE READY DONE

31. Example Policy - Classes of Service for Downstream Involvement Red – Must be involved hands on Yellow – Advise/Consult, but most work in Teams Green – don’t need any involvement Why? To get best results with available resources

32. Pop Quiz What do you think is happening here? Do we have a bottleneck ?

33. Build Quality In

34. Jidoka – Stop the line Don’t let defects accumulate and hurt you later Keep the open defects count LOW

35. Summary Limit work in process: Stop starting, start finishing

36. Want to learn more? Lean-flavored Agile Testing Training by Agilesparks http://www.agilesparks.com/files/AgileTestingAS.pdf Kanban training by Agilesparks http://www.agilesparks.com/files/KanbanforManagers.pdf Contact us at info@agilesparks.com for more information