Kanban six core practices

4,192 views

Published on

I describe the common problem of unbalanced organisations and how Kanban might be a solution.

I also points out that you are not doing Kanban if you do not follow the six practices. Then you are doing something else, that looks like kanban. And guess what, you might not get the expected result out of kanban.

Published in: Technology, Business
1 Comment
6 Likes
Statistics
Notes
  • The most effective presentation of managing flow and balancing supply and demand I've seen - bravo!
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total views
4,192
On SlideShare
0
From Embeds
0
Number of Embeds
10
Actions
Shares
0
Downloads
66
Comments
1
Likes
6
Embeds 0
No embeds

No notes for slide
  • 1)Skapamedvetenhetomproblemet2) Skapavilkaattlösaproblemet3) Skapakunskapattlösaproblemet
  • Draw your board in class and discuss bottlenecks and limits.
  • Do it together in class.
  • Kanban six core practices

    1. 1. Yes we Kanban! Anders Holmberg Christian Ekstrand Johannes Brännström
    2. 2. CHECK IN • 1 min each: – How are you feeling today?
    3. 3. Agenda • 45 min Kanban Theory • 45 min Kanban Simulation • 30 min Discussion: Kanban in your environment
    4. 4. Anders Holmberg • Coach and instructor • • • • • anders.holmberg@softhouse.se Agile Lean Lean Startup Visualize information Internal communication
    5. 5. A common problem Goal Bus Dev Sys Analysis Design Development Test Deploy Problem Capacity Output Strategy How do you handle this today?
    6. 6. Perhaps Kanban? Kanban stops you from working with too much at the same time. Kanban helps you to deliver more without overloading workers. Kanban helps you get a balanced flow of work.
    7. 7. The Kanban Strategy Goal Bus Dev Sys Analysis Design Development Test Problem Kanban says: - No one is allowed to work more than the bottleneck can handle! Strategy Kanban says: - Otherwise the company will produce less! Deploy
    8. 8. Saying no is hard! Is it in anybodys’ responsibility? And Kanban can help you: – – – – – To say NO to low priority work To say NO to too much work at the same time To say NO when you ask your bottleneck to do too much To say NO to new coding until we have finished the delivery To say NO to more development when the receiver is not ready. And sometimes we need this help.
    9. 9. This is Kanban! http://en.wikipedia.org/wiki/Kanban_(development)#Six_core_practices 1. Visualize (the entire flow if possible) 2. Limit Work in progress (based on your bottlenecks capacity) 3. Manage flow (monitor, measure and optimize the whole) 4. Make policies explicit (definition of done, team rules) 5. Implement feedback loops (don’t wait for feedback, build it into the organisation) 6. Improve collaboratively, evolve experimentally (using models and scientific methods)
    10. 10. This is Kanban! http://en.wikipedia.org/wiki/Kanban_(development)#Six_core_practices 1. Visualize (the entire flow if possible) 2. Limit Work in progress (based on your bottlenecks capacity) 3. Manage flow If you are not doing these 6 you are not doing Kanban. (monitor, measure and optimize the whole) 4. Make policies explicit (definition of done, team rules) 5. Implement feedback loops (don’t wait for feedback, build it into the organisation) 6. Improve collaboratively, evolve experimentally (using models and scientific methods)
    11. 11. Remember the slogan 1) Visualize
    12. 12. 2) Limit Work In Progress Goal Bus Dev Sys Analysis Design Development Test Deploy Problem Strategy 3] [Limit = 2] 3] [Limit = 2] 3] [Limit = 2] 3] [Limit = 2] [Limit = 3] Capacity = 2 Capacity = 3 14
    13. 13. 3) Manage Flow Gather & Define Requirements Analyze & Design Develop Test & Accept [1] [3] [4] [2] doing done doing done Limit reached doing done doing Bottleneck Package & Deploy [4] done doing done Available 15
    14. 14. 4) Make Policies Explicit For instance: • Way of working • Limit WIP quantified as a number • Expedite lane • Visualize different prioritization for everyone To make it easier to discuss and improve policies.
    15. 15. 5) Implement Feedback Loops 1st level of feedback: When do YOU get feedback? You (the team) give yourself feedback 2nd level of feedback: You ask the persons receiving your work for feedback 3rd level of feedback: You ask your customer for feedback
    16. 16. 6) Improve Collaboratively, Evolve Experimentally Plan: Do: Check: Act: Decide a new way of working. Set an acceptance criteria. Define a test period. Try the new way of working during the test period. After the test period you evaluate outcome. Decide to keep or throw away the new way of working.
    17. 17. Run Simulation! Really urgent tasks
    18. 18. Getting Started • The game begins in the Standup Meeting at start of Day 9. • Assign workers by dragging them to the story you want them to work on for the day. • When all workers are assigned, click the begin Work Button to have them perform the day’s work. • Workers work a random number between 1 and 6. Or 2 and 12 when the specialists work in their area. • The game ends when Day 30 is complete. Good Luck! Start the game here!
    19. 19. Thank you! Anders Holmberg anders.holmberg@softhouse.se Personal blog: agilcoach.se

    ×