Introduction to kanban lean ghm_02022010

  • 4,440 views
Uploaded on

Introduction to Kanban and lean

Introduction to Kanban and lean

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
4,440
On Slideshare
0
From Embeds
0
Number of Embeds
5

Actions

Shares
Downloads
434
Comments
0
Likes
7

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Introduction to KANBAN & LEAN
    Mads Troels Hansen
    BestBrains, February 2nd 2010
  • 2. Inspiration, theory, examples
    Visual
    Mgt.
    Kaizen
    Kanban
    Lean
    Agile
    Your expectations?
  • 3. WhyKanban and Lean?
  • 4. Kanban and Visual Management (1/3)
    Alignedgoals
  • 5. Kanban and Visual Management (2/3)
    More contribution
  • 6. Kanban and Visual Management (3/3)
    Bottlenecks and Quality
  • 7. Mads Troels Hansen: Kanban Experience
    Agile and Lean Coach at BestBrans
    Agile and Lean Coach, Management Consultant
    Development Director at Omada
    7 different nationalities, products, projects and support, 4 teams, global clients
    Development Director, co-founder at SoftwarePeople
    Products, projects and hosting, 6 teams
    Started Offshore in Bangladesh, SoftwarePeopleLtd, 25+ people
    IT Director at PeopleGroup
    Started Offshore graphical production in Bangladesh.
    Development Manager at NetPeople
    15+ nationalities, 2 teams
    2010
    Scrum extended with Kanban
    Kanban and offshore teams
    Kanban talks, training, coaching
    2008
    Kanban and Visual Management
    Scrumboardswith offshore teams
    2006
    Kanban techniques
    Hyper productive offshore teams
    2004
    Started Offshore production company
    Agile+XP, Task Boards
    2003
    Also experience as developer, architect, project manager.
  • 8. Agenda
    • Introduction w. basic theory (20 min)
    • 9. break (5 min)
    • 10. Kanban, Scrum, Scrumban (~20 min)
    • 11. break: Sandwich (15 min)
    • 12. Examples of Kanban boards (20 min)
    • 13. break (5 min)
    • 14. Kanban on Whiteboard (20 min)
    • 15. 5 steps to get started (5 min)
  • Kanbandevelopment
    A very simple tool
    Adaptive
    Prescriptive
    Extreme
    Programming
    CMMI (ML 3-5)
    Kanban
    SCRUM
    RUP
    ”Whatever”
    9
  • 16. Kanban and kanban
    • Toyota Production System (TPS)
    • 17. TaiichiOhno (大野 耐)
    • 18. A kan-ban
    • 19. A physical card (kan)
    • 20. A signaling device (ban)
  • Lean (TPS) and Kanban
  • 21. FLOW
  • 22. PULL
  • 23. CADANCE
  • 24. Release
    per
    Feature
  • 25. Systems Thinking
  • 26. ValueStreams
  • 27. Limit
    Work-In-Progress
  • 28. Schedulelarge work orders and align resources by workflow
    Schedulesmall work orders and align resources by schedule
    Schedulesmall work orders and align resources by workflow
  • 29. Kanban, Scrum, Scrumban
  • 30. Scrum
    Sprint Planning
    Daily Scrum Meeting
    • 10-15 minutes
    • 34. Three questions
    Burndown Charts
    Product Owner
    • Speaks on behalf of the customer
    • 36. Prioritization
    • 37. Owns product backlog
    Sprint Review
    Scrum Master
    • Responsible for process
    • 39. Support of team
    • 40. Remove empediments
    Scrum Team
    • Cross-functional
    • 41. Delivers
  • Scrum and KanbanTwo process tools
    Scrum vs. Kanban
    Scrum
    Accept test
    Deployment
    Sales
    Analyze
    Dev
    Kanban
  • 42. Pull
    Scrum vs. Kanban
    Kanban
    Downstream pull
    from upstream
    Scrum
    Push from business/product mgt.
  • 43. Taskboard game
    Scrum vs. Kanban
    In Prog
    Review
    Done
    ToDo
    PBL
    A
    Test
    Doc
    Deploy
    B
    C
    D
    E
    F
    In Prog (2)
    Review (2)
    Queue (2)
    Test
    Queue (2)
    Doc
    Queue (2)
    Deploy
    Queue (3)
    PBL
    A
    D
    E
    B
    F
    C
  • 44. Taskboard game
    Scrum vs. Kanban
    New request from a customer
    X
    In Prog
    Review
    Done
    ToDo
    PBL
    X
    A
    Test
    Doc
    Deploy
    B
    C
    D
    E
    F
    In Prog (2)
    Review (2)
    Queue (2)
    Test
    Queue (2)
    Doc
    Queue (2)
    Deploy
    Queue (3)
    PBL
    A
    X
    D
    E
    B
    C
    F
  • 45. Taskboard game
    Scrum vs. Kanban
    New request from a customer
    X
    In Prog
    Review
    Done
    ToDo
    PBL
    X
    A
    Test
    Doc
    Deploy
    B
    C
    D
    E
    F
    In Prog (2)
    Review (2)
    Queue (2)
    Test
    Queue (2)
    Doc
    Queue (2)
    Deploy
    Queue (3)
    PBL
    A
    X
    D
    E
    B
    C
    F
  • 46. Taskboard game
    Scrum vs. Kanban
    New request from a customer
    X
    New bug reported
    Y
    In Prog
    Review
    Done
    ToDo
    PBL
    Y
    A
    Test
    Doc
    Deploy
    X
    B
    C
    D
    E
    F
    In Prog (2)
    Review (2)
    Queue (2)
    Test
    Queue (2)
    Doc
    Queue (2)
    Deploy
    Queue (3)
    PBL
    A
    X
    Y
    F
    B
    D
    C
    E
  • 47. Taskboard game
    Scrum vs. Kanban
    New request from a customer
    X
    New bug reported
    Y
    In Prog
    Review
    Done
    ToDo
    PBL
    Y
    A
    Test
    Doc
    Deploy
    X
    B
    C
    D
    E
    F
    In Prog
    Review (2)
    Queue (2)
    Test
    Queue (2)
    Doc
    Queue (2)
    Deploy
    Queue (3)
    PBL
    A
    X
    Y
    F
    B
    D
    C
    E
  • 48. Taskboard game
    Scrum vs. Kanban
    New request from a customer
    X
    New bug reported
    Y
    In Prog
    Review
    Done
    ToDo
    PBL
    Y
    A
    Test
    Doc
    Deploy
    X
    B
    C
    D
    E
    F
    In Prog
    Review (2)
    Queue (2)
    Test
    Queue (2)
    Doc
    Queue (2)
    Deploy
    Queue (3)
    PBL
    A
    X
    Y
    E
    B
    C
    D
    F
  • 49. Taskboard game
    Scrum vs. Kanban
    New request from a customer
    X
    New bug reported
    Y
    In Prog
    Review
    Done
    ToDo
    PBL
    Y
    A
    Test
    Doc
    Deploy
    X
    B
    C
    Problem with test server
    D
    E
    F
    In Prog
    Review (2)
    Queue (2)
    Test
    Queue (2)
    Doc
    Queue (2)
    Deploy
    Queue (3)
    PBL
    A
    X
    Y
    E
    B
    C
    D
    F
    Queue full
  • 50. Taskboard game
    Scrum vs. Kanban
    New request from a customer
    X
    New bug reported
    Y
    In Prog
    Review
    Done
    ToDo
    PBL
    Y
    A
    Test
    Doc
    Deploy
    X
    B
    C
    Fixing the test server
    D
    E
    F
    In Prog
    Review (2)
    Que (2)
    Test
    Queue (2)
    Doc
    Queue (2)
    Deploy
    Queue (3)
    PBL
    A
    X
    Y
    E
    D
    C
    B
    F
  • 51. Taskboard game
    Scrum vs. Kanban
    Scrum: Scope commitment more focus to developers.
    New request from a customer
    X
    New bug reported
    Y
    In Prog
    Review
    Done
    ToDo
    PBL
    Y
    A
    Test
    Doc
    Deploy
    X
    B
    C
    D
    Kanban: Visualize bottlenecks fast, and enable frequent business prioritization.
    E
    F
    In Prog
    Review (2)
    Queue (2)
    Test
    Queue (2)
    Doc
    Queue (2)
    Deploy
    Queue (3)
    PBL
    A
    X
    Y
    E
    D
    C
    B
    F
  • 52. Business prioritization
    Scrum
    Don't interrupt WIP and you may only adjust our work plan every iteration.
    Kanban
    Don't interrupt WIP and you may change prioritization any time.
    Scrum vs. Kanban
  • 53. Commitment and goals
    Scrum
    Commit to a scope
    Kanban
    Commit to deliver working features within a time limit.
    SLA: “…always deliver within 14 days…”
    Scrum vs. Kanban
  • 54. Planning
    Scrum
    Combined planning and release cycles.
    Kanban
    Planning and release can be separated.
    Frequent planning with release interval related to cost of release and business feedback.
    Scrum vs. Kanban
  • 55. WIP
    Scrum
    Limit WIP pr. iteration
    Kanban
    Limit WIP pr. workflow state
    Scrum vs. Kanban
  • 56. Roles
    Scrum
    Product Owner
    Scrum Master
    Team
    Kanban
    None prescribed!
    An Agile Project Manager might be valuable to focus on the full value stream
    Scrum vs. Kanban
  • 57. Iterations
    Scrum
    Sprints, one cadence with
    Planning
    Process improvement
    Release
    Kanban
    No iteration
    Can chose when to do planning, Process improvement, release etc.
    Scrum vs. Kanban
  • 58. Backlogs
    Scrum
    Product Backlog
    Sprint Backlog
    (Impediment backlog!)
    Kanban
    Queues
    Maybe combine with a Backlog of requirements
    Scrum vs. Kanban
  • 59. Teams
    Scrum
    Cross-functional team
    Kanban
    Specialists
    Different roles
    Can also be cross-functional
    Scrum vs. Kanban
  • 60. Reporting
    Scrum
    ProductBacklogBurndownchart
    Sprint BacklogBurndown
    Kanban
    Cumulative Flow Diagrams (CFD)
    Scrum vs. Kanban
  • 61. Estimating and velocity
    Scrum
    Estimate relative size
    Measure velocity
    Use velocity for planning
    Kanban
    None… might make sense to do it
    Break down work at same size
    Throughput instead of velocity
    Scrum vs. Kanban
  • 62. Quick summary
    Scrum vs. Kanban
  • 63. EXAMPLES OF KANBAN BOARDS
  • 64.
  • 65.
  • 66. Traditional task boards
  • 67. Just getstarted
  • 68. Devs, tests, technicalwriter, operations, support
  • 69. Personal Kanban
  • 70. Traditional task board extended with limits
  • 71. Kanban board
  • 72. Kanban board
  • 73. Kanban board
  • 74. Kanban board
  • 75. Kanban board
  • 76. Virtual Kanban board (Custom solution against TFS)
  • 77. Rally
  • 78. Version One
  • 79. Target Process
  • 80. Jira Greenhopper
  • 81. KanbanonWhiteboard
  • 82.
  • 83.
  • 84. Kanban – Get started
    My Top 5
    My Top 5
    Draw your end-to-end process (Value Stream)
    Map your process to a physical Task board
    Start using the board
    Limit work-in-process with WIP limits
    Measure cycle time and lead time
    n. Find bottlenecks, do Kaizen and improve
    Use 2 minutes to create your personal list
  • 85. Kanban – Take Away
    A Kanban system, starts to focus on flow and cycle time of delivered work and gives a way to visualize and resolve bottlenecks
  • 86. Thank you
    mth@bestbrains.dk
    People don’t resist change, they resist being changed.
    - Peter Scholtes
    @MadsTH
  • 87. Some references
    Lean Software Development - An Agile Toolkit, Mary & Tom Poppendieck, 2003
    Implementing Lean Software Development, Mary & Tom Poppendieck, 2007
    The Enterprise and Scrum, Ken Swaper, 2007
    Factory Physics, W. Hopp, 3rd edition, 2008
    Agile management, David Andersson, 2004
    Scrumban, Corey Ladas, 2009
    Kanbanvs Scrum – A practical guide, Henrik Kniberg, April 2009
    Kanban intro, Karl Scotland, http://availagility.wordpress.com/2008/10/28/kanban-flow-and-cadence/
    YahooGroup: Kanbandev
    Software Excellence http://www.bestbrains.dk/dansk.aspx/Rådgivning