• Save
Kanban 101 - 2 Flow basics
Upcoming SlideShare
Loading in...5
×
 

Kanban 101 - 2 Flow basics

on

  • 8,113 views

Kanban 101 workshop by John Goodsen and Michael Sahota. ...

Kanban 101 workshop by John Goodsen and Michael Sahota.

This module is about the basics of flow: batch size, limiting work in process and bottlenecks (theory of constraints).

Please ask us if you would like PPT version.

Statistics

Views

Total Views
8,113
Views on SlideShare
2,777
Embed Views
5,336

Actions

Likes
3
Downloads
0
Comments
1

6 Embeds 5,336

http://agilitrix.com 5259
http://www.agilitrix.com 69
http://webcache.googleusercontent.com 4
http://translate.googleusercontent.com 2
http://localhost 1
https://www.google.com 1

Accessibility

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

CC Attribution-NonCommercial LicenseCC Attribution-NonCommercial License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel

11 of 1

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • [5 min]

Kanban 101 - 2 Flow basics Kanban 101 - 2 Flow basics Presentation Transcript

  • The Basics of Flow (How to get stuff done) Michael Sahota & John Goodsen
  • Exercise: What is most important?
    • Form Pairs/Triads
    • Rank/order by importance:
      • Reducing multitasking
      • Reducing batch sizes
      • Identifying bottlenecks
    • As class, review rankings and reasoning
  • MultiTasking Exercise: Name Game Dave Lisa Robert 1 Developer 3– 6 customers Henrik Kniberg
  • Summary: Improve cycle time and productivity through focus ... becomes ...
  • What is your team like? Todo Doing Done this week Avg cycle time: days Todo Doing Done this week Avg cycle time: days Henrik Kniberg orem ipsum dolor sit amet, co nse ctetur orem ipsum dolor sit amet, co nse ctetur orem ipsum dolor sit amet, co nse ctetur orem ipsum dolor sit amet, co nse ctetur orem ipsum dolor sit amet, co nse ctetur orem ipsum dolor sit amet, co nse ctetur orem ipsum dolor sit amet, co nse ctetur orem ipsum dolor sit amet, co nse ctetur orem ipsum dolor sit amet, co nse ctetur orem ipsum dolor sit amet, co nse ctetur orem ipsum dolor sit amet, co nse ctetur orem ipsum dolor sit amet, co nse ctetur 3 orem ipsum dolor sit amet, co nse ctetur orem ipsum dolor sit amet, co nse ctetur orem ipsum dolor sit amet, co nse ctetur orem ipsum dolor sit amet, co nse ctetur orem ipsum dolor sit amet, co nse ctetur orem ipsum dolor sit amet, co nse ctetur orem ipsum dolor sit amet, co nse ctetur 20 orem ipsum dolor sit amet, co nse ctetur orem ipsum dolor sit amet, co nse ctetur orem ipsum dolor sit amet, co nse ctetur orem ipsum dolor sit amet, co nse ctetur orem ipsum dolor sit amet, co nse ctetur orem ipsum dolor sit amet, co nse ctetur orem ipsum dolor sit amet, co nse ctetur orem ipsum dolor sit amet, co nse ctetur orem ipsum dolor sit amet, co nse ctetur orem ipsum dolor sit amet, co nse ctetur orem ipsum dolor sit amet, co nse ctetur orem ipsum dolor sit amet, co nse ctetur orem ipsum dolor sit amet, co nse ctetur orem ipsum dolor sit amet, co nse ctetur orem ipsum dolor sit amet, co nse ctetur orem ipsum dolor sit amet, co nse ctetur
  • Exercise: Penny Flow Game
    • Get in groups of 4 to 6 people
    • One customer
    • Everyone else is a worker
    • How long does it take to deliver?
    • Start with batch size 20
    • Workers need to flip over coins
      • Left arm only. Right needs to be behind your back.
    • Time the results
  • To improve cycle time, reduce batch size
  • Little’s Law is mathematical model relating WIP to cycle time
  • Theory of Constraints & Bottlenecks – Where is the work stuck?
    • Demo:
      • http://tocca.com.au/Services/demoOperations.htm
  • Discussion: What do you choose?
    • Have people waiting for work
    • or
    • Work waiting for people
  • Exercise: Ranking reprise
    • Form Pairs
    • Rank/order by importance:
      • Reducing multitasking
      • Reducing batch sizes
      • Identifying bottlenecks
    • As class, review rankings and reasoning