Intro to Kanban - Ofer Cohen - Agile Israel 2014

1,202 views

Published on

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,202
On SlideShare
0
From Embeds
0
Number of Embeds
529
Actions
Shares
0
Downloads
13
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Intro to Kanban - Ofer Cohen - Agile Israel 2014

  1. 1. What is Kanban 5 Core Kanban Properties 看板 ”Visual Card” 6/1/2014 1 Ofer Cohen AgileSparks
  2. 2. 1. Visualize the Flow Start with the current process, Visualize the flow to deliver value Analysis Design Dev QA UAT 6/1/2014 2
  3. 3. 1. Visualize the Flow Start with the current process, Evolve it Backlog Analysis Design Dev QA UAT Done In Process Done In Process Done In Process Done In Process Done In Process Done 6/1/2014 3
  4. 4. 2. Limit Work In Progress Backlog Analysis Design & Dev Validation Done In Process Done In Process Done In Process Done 2 4 4 Work items pull into the next phase only when there is a space Each step can only have so many work items. 6/1/2014 4
  5. 5. 3. Observe (Measure and Manage) Flow Moving one piece at a time between stages in a workflow as opposed to Moving batches of work between stages in a workflow 6/1/2014 5
  6. 6. 3. Measure & Manage Flow 0 10 20 30 40 50 60 70 Sample Cumulative Flow Backlog Analysis Design Dev QA UAT Done Lead TimeWIP 6/1/2014 6
  7. 7. 4. Make Process Policies Explicit 7 Definition of Done: • Goal is clear • First task defined Definition of Done: • code clean and checked in truck • Integrated & regression tested Definition of Done: • All tests passed • All tests documented Definition of Done: • User signed off test env • user guide upated Definition of Done: •system running on prod env for 1 day error free 2 3 5 2 3 6/1/2014
  8. 8. 5. Improve Collaboratively/Improve the system • Implement feedback loops • System Thinking • Continuously identify and eliminate waste • Evolve experimentally 6/1/2014 8
  9. 9. Some Basic Figures State of Agile Survey (2013) - “Kanban continues to gain popularity (7% increase)” In our implementations we are seeing many more organizations choosing Kanban 96/1/2014
  10. 10. Scrum is hard to swallow • Scrum is a Revolutionary approach – Difficult for the organization to change and Implement • Kanban is an Evolutionary approach – Start with current process and improve it – Easy to implement 6/1/2014 10
  11. 11. Scrum challenges and Kanban Solution(1) • Scrum forces role changes, new team structure, new ceremonies • Kanban starts with the current process, evolves – more agile method for change management Scrum Master?? Product Owner ?? Cross Functional Teams ?? What about Current Roles (TL??) 6/1/2014 11
  12. 12. Scrum challenges and Kanban Solution(2) • Most Scrum implementation = Scrum in the teams • Most waste is on the FLOW (collaboration between BU, Hand-offs, E2E delivery) 6/1/2014 12
  13. 13. Scrum challenges and Kanban Solution (3) • Many Scrum teams are doing mini-waterfalls sprints • Kanban basics is limit WIP that eliminates mini waterfall and forces short cycle time 6/1/2014 13
  14. 14. Scrum challenges and Kanban Solution(4) • Scrum encourages micro management of teams (hourly tasks, hours done reporting, strong sprint commitment) • Kanban focuses on delivery and emphasizes Stop Starting, Start Finishing! 6/1/2014 14
  15. 15. Scrum challenges and Kanban Solution(6) • Scrum->Avoid Sprint content changes – No Soup for you! Wait for next Sprint! • Kanban focuses on highest value feature and getting it done through the flow 6/1/2014 15
  16. 16. Summary • Do it the evolutionary way • Focus on flow, Focus on E2E delivery • Kanban – more agile implementation! 6/1/2014 16

×