Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

(Agile Sydney version) Stop Starting and Start Finishing: An Introduction to Kanban

6,916 views

Published on

An introduction to Kanban given at Agile Sydney

Published in: Technology

(Agile Sydney version) Stop Starting and Start Finishing: An Introduction to Kanban

  1. 1. Stop Starting and Start Finishing:An introduction to Kanban<br />j.c.yip@computer.org, jcyip@thoughtworks.com<br />http://jchyip.blogspot.com<br />@jchyip<br />
  2. 2. Problem: overburdening<br />
  3. 3.
  4. 4.
  5. 5.
  6. 6.
  7. 7. Problem: Effective Change<br />
  8. 8. Dramatic change is risky<br />
  9. 9. Setup conditions for improvement<br />Visualise our workflow<br />Limit our work-in-progress<br />Measure our performance<br />Improve<br />
  10. 10. Visualise our workflow<br />
  11. 11.
  12. 12.
  13. 13.
  14. 14. Show what is happening, not what should be happening<br />
  15. 15. Limit our work-in-Progress<br />
  16. 16.
  17. 17.
  18. 18.
  19. 19.
  20. 20.
  21. 21.
  22. 22. Measure our performance<br />
  23. 23.
  24. 24.
  25. 25.
  26. 26.
  27. 27. Performance is not just about time<br />Productivity: cycle time, ROI<br />Quality: UAT defects, released defects, user satisfaction<br />Cost: burn rate, cost per work item, overall project cost<br />Morale: engagement, employee satisfaction<br />
  28. 28. improve<br />
  29. 29. Standard Agile improvement tricks<br />Daily stand-ups<br />Retrospectives<br />
  30. 30. New improvement tricks<br />Stop-the-line: free up the WIP limit<br />Quality circle: form a team to figure something out<br />Operations review: regular meeting to analyse past performance, outliers, etc.<br />
  31. 31. Change != Improvement<br />
  32. 32.
  33. 33. Encourage self-forming improvement teams over scheduled improvement events<br />
  34. 34. Learning more<br />
  35. 35.
  36. 36. Core Properties of Kanban<br />Visualise Workflow<br />Limit Work-In-Progress<br />Measure and Manage Flow<br />Make Process Policies Explicit<br />Use Models to Recognize Improvement Opportunities<br />
  37. 37. Emergent Properties of Kanban<br />Prioritise Work by Cost of Delay<br />Optimise Value with Classes of Service<br />Spread Risk with Capacity Allocation<br />Encourage Process Innovation<br />Manage Quantitatively<br />
  38. 38. Where to learn more<br />http://finance.groups.yahoo.com/group/kanbandev/<br />Books:<br />Kanban by David J. Anderson<br />Scrumban by Corey Ladas<br />http://www.limitedwipsociety.org/<br />http://www.meetup.com/The-Sydney-Limited-WIP-Society/<br />
  39. 39. First steps?<br />Share ideas and commitment for how to get started<br />

×