Some Kanban experiencesand FAQsanders.sixtensson@softhouse.seLean Gathering #3 Karlskrona
Some problems where Kanban has been used• Long cycle times• Scrum do not fit• Only specialists – no generalists
What is Kanban?• A simple pull based flow• Kan = Visual, Ban = Card or Board                                      - Bugs t...
Kanban – limits WIP             Attack with:                                • WIP Limits                                • ...
Kanban – simplest version                            5
Some FAQs – and the short answers•   Tool support?                             •   No – but…•   Do we need to have a limit...
What to do when Limits and/or waiting stops me to work?   General answer – anything that make an ongoing task to move is a...
Extend your board – if it adds value!                          Analyze&                        Verify        Deploy       ...
Metrics – leading or lagging indicator!•   “One of the most powerful tools are Cumulative Flow Diagram (CFD)” – Donald    ...
Make ReadyGetting started1.   Agree clearly with stakeholders your Make     Ready and Def-of-Done2.   Select what colums t...
More to read  http://www.limitedwipsociety.org/
Scrum                      vs                        (simple) Kanban•   Early and frequent delivery of                    ...
Upcoming SlideShare
Loading in …5
×

Some Kanban Experiences - Anders Sixtensson - LTG-3

759 views

Published on

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

No Downloads
Views
Total views
759
On SlideShare
0
From Embeds
0
Number of Embeds
49
Actions
Shares
0
Downloads
11
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Some Kanban Experiences - Anders Sixtensson - LTG-3

  1. 1. Some Kanban experiencesand FAQsanders.sixtensson@softhouse.seLean Gathering #3 Karlskrona
  2. 2. Some problems where Kanban has been used• Long cycle times• Scrum do not fit• Only specialists – no generalists
  3. 3. What is Kanban?• A simple pull based flow• Kan = Visual, Ban = Card or Board - Bugs to fix - Trouble Reports - Projects - Assignments - Features - Tasks - … any work…
  4. 4. Kanban – limits WIP Attack with: • WIP Limits • Smaller batches • Pull Work-in-progress (100) (75)(3) (5) Cycle time = Throughput (20) (25) Attack with: • Protect your bottleneck • Expand bottleneck • Remove waste 4
  5. 5. Kanban – simplest version 5
  6. 6. Some FAQs – and the short answers• Tool support? • No – but…• Do we need to have a limit? • Yes• Do we need a Kanban leader? • Yes, to own To-Do• Do we need to estimate size? • No, hopefully not• If tasks are very different in size? • Split• But it is only Nisse that can do that! • Is that good?• Does it scale – we are a project of 100 • Yes – different people? levels• Can I keep my waterfall phases? • Yes, unfortunately• Not working full time? • No problem• Expediters, Silver bullets, Rockets.. • Own Swim lane• Other metrics? • Yes
  7. 7. What to do when Limits and/or waiting stops me to work? General answer – anything that make an ongoing task to move is always better than pulling in new work! The following rules where defined at Maintenance team we worked with: 1. Can I do something to shorten waiting time? 2. Can someone in the team help me to shorten waiting time? 3. Can I help someone else that has been blocked? 4. Can I do some pro-active work to eliminate future waiting/blocking? Discuss with Kanban leader. 5. Who can I sit next to to ”pair-work”? Discuss with Kanban leader. 7
  8. 8. Extend your board – if it adds value! Analyze& Verify Deploy Develop [3] Design [1] &Accept [4] [4] doing done doing done doing done doing doneSLA class 1[6]SLA class 2[4]SLA class 3[2] Expedite [2]CR PR Bug Maint Expedite 8
  9. 9. Metrics – leading or lagging indicator!• “One of the most powerful tools are Cumulative Flow Diagram (CFD)” – Donald Reinertsen – FLOW, 2nd generation Lean Product Development Measured queue size Measured cycle time 9
  10. 10. Make ReadyGetting started1. Agree clearly with stakeholders your Make Ready and Def-of-Done2. Select what colums to start with. Start simple3. Assign limits. Start with 2 * team members in each column4. Find a good place for board and daily meetings SE1091531 Planned ready: 2010-03-03 Start date End date Objects in test mode is presented in Power System event list5. Have first meeting and agree on meeting Meeting scheduled with Stefan K and Shirley. rule Server changes only? (d) IIII (h) 2+4+36. Do – learn - adapt Prio: 1 Resource Release Carl-Johan 4.2.2 Aberger 10
  11. 11. More to read http://www.limitedwipsociety.org/
  12. 12. Scrum vs (simple) Kanban• Early and frequent delivery of • Early and frequent value delivery of value• • Clear sprint goals• Clear sprint goals Value and • Self directing teams Waste• Self directing teams Continuous Manage the • Pull• Pull Improvement Flow • Reduced batch-size• Reduced batch-size Optimize the People and whole Leadership • Just-in-time planning• Just-in-time planning • Time boxed• Time boxed • Continuous• Continuous Improvement Improvement 12

×