Moving to Kanban<br />Tomas Sakalauskas<br />
About me<br />Lost 13 years in pursuit of best SW development methodology …<br />… to find out there is none<br />Currentl...
Disclaimer<br />I have no clue what Kanban is<br />It sounds good, like Agile or Scrum, so people should attend the sessio...
Stop starting start finishing<br />
Why Kanban?<br />Minimal entry barrier<br />Flexible resource planning and using<br />Sometimes time-boxing doesn’t work<b...
You have all it takes!<br />Start with what you do now<br />Agree to pursue incremental, evolutionary change<br />Respect ...
Kanban properties<br />Visualize workflow<br />Limit WIP<br />Manage flow<br />Make Process Policies Explicit<br />Improve...
#1. Visualize workflow<br />Shared understanding of where you are<br />It may be ugly at first<br />
The most basic board<br />
#2. Limit WIP<br />Less multitasking – less context switching<br />Better quality<br />No WIP limit = queue!<br />Queues i...
Limits<br />
Backlog<br />
Lifecycle<br />
Queue<br />
Day 0<br />
Day N<br />
Pull not push<br />Work items should be pulled into available spaces<br />If stuck, something should be improved:<br />Hel...
Releases<br />Decouple release from development<br />Release whatever has been completed since the last release<br />Regul...
Blockers<br />
Priority Lane<br />
Multiple Projects<br />
Multiple Projects<br />
Deployment<br />
Kanban team<br />Continuous planning<br />Daily standup:<br />What can we do with blockers?<br />What can we do with bottl...
#3. Measure and improve flow<br />Velocity could also mean a rate at which defects are produced!<br />Flow metrics:<br />A...
#4. Make Process Policies Explicit<br />How to improve when no-one knows how it’s actually done?<br />Don’t spend too much...
#5. Improve collaboratively<br />There is no Kanban Software Development Process	orKanban Project Management Method<br />V...
Kanban in Eylean team<br />Two asynchronous processes:<br />Goal oriented JIT planning: <br />Decisions deferred till info...
Product development is complex<br />Self-organizing, non-linear, feedback systems are inherently unpredictable, they are u...
Celebrate failures too!<br />Storing avoidance of failure patterns is a more successful strategy for the brain than imitat...
Questions?<br />tomas.sakalauskas@prewise.lt<br />
Upcoming SlideShare
Loading in …5
×

Tomas Sakalauskas: Moving to kanban

1,349 views

Published on

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,349
On SlideShare
0
From Embeds
0
Number of Embeds
239
Actions
Shares
0
Downloads
19
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Tomas Sakalauskas: Moving to kanban

  1. 1. Moving to Kanban<br />Tomas Sakalauskas<br />
  2. 2. About me<br />Lost 13 years in pursuit of best SW development methodology …<br />… to find out there is none<br />Currently<br />Managing director of Prewise, UAB<br />Product manager of Eylean<br />
  3. 3. Disclaimer<br />I have no clue what Kanban is<br />It sounds good, like Agile or Scrum, so people should attend the session ;)<br />
  4. 4. Stop starting start finishing<br />
  5. 5. Why Kanban?<br />Minimal entry barrier<br />Flexible resource planning and using<br />Sometimes time-boxing doesn’t work<br />Focus on whole value stream, eliminates inessential waste:<br />Artificial work breakdown<br />Estimation, planning and retrospectives for artificial stories<br />Supports integrated processes<br />
  6. 6. You have all it takes!<br />Start with what you do now<br />Agree to pursue incremental, evolutionary change<br />Respect the current process, roles, responsibilities & titles<br />
  7. 7. Kanban properties<br />Visualize workflow<br />Limit WIP<br />Manage flow<br />Make Process Policies Explicit<br />Improve Collaboratively<br />
  8. 8. #1. Visualize workflow<br />Shared understanding of where you are<br />It may be ugly at first<br />
  9. 9. The most basic board<br />
  10. 10. #2. Limit WIP<br />Less multitasking – less context switching<br />Better quality<br />No WIP limit = queue!<br />Queues increase cycle time, risk and overhead<br />
  11. 11. Limits<br />
  12. 12. Backlog<br />
  13. 13. Lifecycle<br />
  14. 14. Queue<br />
  15. 15. Day 0<br />
  16. 16. Day N<br />
  17. 17. Pull not push<br />Work items should be pulled into available spaces<br />If stuck, something should be improved:<br />Help needed in downstream processes<br />WIP limits are wrong for the team<br />The task transitioned too early<br />Don’t miss a learning opportunity<br />
  18. 18. Releases<br />Decouple release from development<br />Release whatever has been completed since the last release<br />Regular releases without artificialness that iterations impose<br />Goal oriented releases<br />Release when it’s ready<br />Meaningful releases without the risks of last-nights work imposed by time-boxing<br />
  19. 19. Blockers<br />
  20. 20. Priority Lane<br />
  21. 21. Multiple Projects<br />
  22. 22. Multiple Projects<br />
  23. 23. Deployment<br />
  24. 24. Kanban team<br />Continuous planning<br />Daily standup:<br />What can we do with blockers?<br />What can we do with bottlenecks?<br />How to move WIP items faster?<br />It’s OK to find defect while packing the release. Pull the feature or delay the release<br />
  25. 25. #3. Measure and improve flow<br />Velocity could also mean a rate at which defects are produced!<br />Flow metrics:<br />Active WIP vs. buffered WIP<br />Active time / cycle time<br />Blocked time / cycle time<br />Outcome metrics:<br />Bugs in process<br />Failure demand / value demand<br />
  26. 26. #4. Make Process Policies Explicit<br />How to improve when no-one knows how it’s actually done?<br />Don’t spend too much time – policies will evolve<br />Example policies:<br />Kanban board columns<br />WIP limits<br />State transition policies<br />
  27. 27. #5. Improve collaboratively<br />There is no Kanban Software Development Process orKanban Project Management Method<br />Value stream is built by people for people<br />Improvement actions are agreed by consensus<br />
  28. 28. Kanban in Eylean team<br />Two asynchronous processes:<br />Goal oriented JIT planning: <br />Decisions deferred till information is available<br />The only questions to be answered:<br />What should be done RIGHT NEXT and WHY?<br />Production:<br />Do your BEST on current feature<br />Finish before you start!<br />Spontaneous improvements to process and product<br />
  29. 29. Product development is complex<br />Self-organizing, non-linear, feedback systems are inherently unpredictable, they are uncontrollable<br />D. Meadows<br />I wish someone told me this 13 years ago ;)<br />
  30. 30. Celebrate failures too!<br />Storing avoidance of failure patterns is a more successful strategy for the brain than imitation of success<br />ALE2011 closing keynote by David Snowden<br />
  31. 31. Questions?<br />tomas.sakalauskas@prewise.lt<br />

×