Kanban intro

721 views

Published on

An introduction to Kanban I presented with Flavius Stef at the Bucharest Agile Meetup Group in February 2014. See the event details on http://www.meetup.com/The-Bucharest-Agile-Software-Meetup-Group/events/146222892/. See http://mozaicworks.com for articles and events about Kanban and agile

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

No Downloads
Views
Total views
721
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
9
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Kanban intro

  1. 1. Intro Kanban Evolutionary change through visualization, flow management and collaboration
  2. 2. Agenda 19:00 19:50 20:00 20:30 21:00 – – – – – Welcome & Talk: Intro to Kanban Open Space Intro + market place First Open Space slot Second Open Space slot Closing
  3. 3. Let's get to know each other
  4. 4. Us
  5. 5. Tokio Imperial Palace – East Garden
  6. 6. 5 Business needs for Kanban ● Better organize work ● Reduce release cycles ● ● ● Reduce management overhead (self-organization) Complement and/or replace Scrum (eg. for maintenance) Improve quality
  7. 7. What is Kanban? Change management tool with six properties – Visualize your workflow – Limit work in progress – Measure and manage flow – Make policies explicit – Implement feedback loops – Improve collaboratively, evolve experimentally
  8. 8. How to adopt Kanban?
  9. 9. What are your value streams? Need ??? Your value stream(s) Cashing the €€€
  10. 10. Understand how you work (Value Stream Mapping) Brainstorm idea Detail idea Sketch UI Code Test Deploy
  11. 11. Visualize work to coordinate Ideas Features UI design Code Test Deploy
  12. 12. Limit WIP to improve flow Ideas Features (5) UI design (4) Code (2) Test (1) Deploy (5)
  13. 13. Focus on flow Add support for Romanian Started on: 20 Jan Finished: 24 Jan 1 2 3 4 5 6 7 8 9 10 11 Cycle Time
  14. 14. Explicit policies Ideas Features (5) UI design (4) Code (2) Test (1) Refactored Code Review Deploy (5)
  15. 15. Prioritize work Ideas Features (5) UI design (4) Most important Code (2) Test (1) Deploy (5)
  16. 16. Deliver often Sep 2008 – Jan 2013
  17. 17. Meetings ● Daily Meeting ● Release Planning ● Queue Replenishment ● Retrospectives ● Demos
  18. 18. How to use Kanban for change?
  19. 19. Read the Board and Act
  20. 20. Read the Board and Act: Column Full Bottleneck Ideas Features (5) UI design (4) Code (2) Test (3) Deploy (5) √ √ Use Theory of Constraints (ToC) to deal with bottlenecks
  21. 21. Read the Board and Act: Failure demand Ideas Features (5) UI design (4) Code (2) Test (3) Deploy (5) Improve quality: add/change practices, update explicit policies
  22. 22. Read the Board and Act: Useless Work Ideas Features (5) To Do UI design (4) Doing Code (2) Test (3) Deploy (5) Done Other work Retrospective using VSM & change process accordingly
  23. 23. Read charts and act: High Cycle time Why did this happen? Add support for Romanian Started on: 20 Jan Finished: 24 Jan 1 2 3 4 5 6 7 8 9 10 11 Cycle Time Change process to improve flow
  24. 24. Periodic Retrospectives ● Pick an area to focus on ● Tell the story of the last 1-2 weeks ● Everyone writes on post-its what went well ● Everyone writes on post-its what could be improved ● Discuss issues ● Define actions until next retrospective ● Plan them, add them on the board
  25. 25. Why Kanban? ● Minimally invasive – Start with what you have ● Balance demand with capacity ● Foster collaboration ● Focus on improvements ● Get stuff done sooner ● Proven successful elsewhere
  26. 26. THANKS! flavius.stef@mozaicworks.com @FlaviusStef alex.bolboaca@mozaicworks.com @alexboly
  27. 27. Picture credits ● http://www.flickr.com/photos/jaimeperez/2753098339/in/phot ostream/ ● http://thenounproject.com/noun/scroll/#icon-No1629 ● http://thenounproject.com/noun/scroll/#icon-No485

×