Successfully reported this slideshow.

How to Get Started with Kanban, and Why


Published on

Kanban 101, with a bit of agile basics and Kanban 201

Published in: Technology
  • Nice one - easy to get the concept. I need to change the way we work at the office, was studying http:/ lately with great interest, but found your presentation even more informative. Thank you!
    Are you sure you want to  Yes  No
    Your message goes here

How to Get Started with Kanban, and Why

  1. 1. KanbanIn Software Development Ingvald Skaug img:
  2. 2. What Is Kanban? Intro What Is Kanban Why FlowLightweight framework for evolutionary change, Why Kanbanstep-by-step improvementEncourages continuous flowNot a process Some background: David Anderson: The Principles of the Kanban Method
  3. 3. Kanban:What Is Kanban? Most adaptive tool (Number = artifacts) ill.: Henrik Kniberg, Kanban and Scrum - making the most of both (with Mattias Skarin)
  4. 4. Why Flow? Intro What Is Kanban Why Flow Inestimable work Why Kanban Unplanned work Unclear work Blocked work - need input from unavailable stakeholder Parking - unfinished work, - waiting b/c of interruptions, multi-tasking Changed work/ requirements Legacy code Normative estimates => tech debt Specialists => uncertain accessJørn Ola Birkeland, Bekk, at XP2010,Experience report: From a timebox tangle to a more flexible flow
  5. 5. Why Kanban? Intro What Is Kanban Why FlowYou can: Why KanbanStart where you areManage change, improve step by stepExpose problems on quality and processEnable higher qualityMore predictable delivery, due date performanceSustainable developmentBalance demand against capacityIncrease trust with customersImprove productivityMore agile organization...Seems like a tall order...
  6. 6. Everything Is Connected Why Kanban
  7. 7. Start: Visualize + WIP Limit Why Kanban Everything Is Connected
  8. 8. Simple Kanban "Kanban 101" / How-to1. Visualize!2. Limit WIP! WIP = work in progress Simple = not easyimg: background:
  9. 9. Visualize! Kanban 101 Visualize Limit WIP Use a Kanban board Reflect real workflow Dashboard visible for everyone Transparent policies WIP limits Specific column names - dont use "Done"...
  10. 10. Why Visualize? Agile Basics Visualize Limit WIP=> Shared mental model=> More engaged stakeholders=> More effective thinking, collaborationEx.: Kanban board,permanently visible to, management, sales... from Tom Wujecs TED talk
  11. 11. Limit WIP! Kanban 101 Visualize Limit WIPStart with generous limitsBetter with big limits than no limits- no limits, no improvement- big limits: minimize resistanceKeep WIP limits visible on Kanban board WIP = work in progress
  12. 12. Why Limit WIP? Agile Basics Visualize Limit WIPWork in progress expires- e.g., requirements change over time WIP = work in progress ill.: Aslak Hellesøy, Smidig 2009: Kanban for nybegynnere
  13. 13. Why Limit WIP? Agile Basics Visualize Limit WIPReduce multi-tasking Some background, ill.: Karl Scotland: Kanban, Flow and Cadence
  14. 14. Why Limit WIP? Agile Basics Visualize Limit WIPExpose quality and process problems- like bottlenecks WIP = work in progress
  15. 15. Q?Simple Kanban1. Visualize!2. Limit WIP! Keep It Simple Be Pragmatic Flow
  16. 16. Kanban vs Scrum Kanban ScrumBatching of work, Works with anything Iteration (+/- 30d),feedback-loop Natural fit: continuous flow sprint backlog to demoTolerance for Yes (with flow) - swimlanes, classes of No, process needs hacking (e.g.,variations, distractions service extra buffer)Control mechanism WIP limit Commitment - stand-up (personal) - sprint: dates, features (team)Initial change Small - low threshold Revolution - prescribed processEventual changes in Evolution - step by step improvements No, Scrum is a fixed processprocess in "process under Kanban" regarding its artifactsWhat can improve If you keep visualizing, limiting WIP: XP practices etc pretty much everythingEstimating/ Works with anything. Estimating needed for burn-downPredictability Best: use lead time after the fact as predictor, not detailed estimatesSpecialists No problem Should be cross-functional teamsSome background: (Kanban and Scrum - making the most of both)
  17. 17. Forward "Kanban 201"David J Anderson: 5 core properties of a Kanbanimplementation 1. Visualize Workflow 2. Limit work-in-progress 3. Measure & Manage Flow 4. Make Process Policies Explicit 5. Use Models to Recognize Improvement Opportunities Background: David Anderson: Five Core Properties of a Kanban Implementation
  18. 18. Forward "Kanban 201"QualityTech DebtFlowClasses of ServiceSlackCadence - separate development, deliveryMetrics a small selection Some more: Aspects of Kanban, by Karl Scotland, including cadence, slack Dennis Stevens on SLAs in Kanban, including cost of delay Classes of Service and Policies, by David Joyce Kanban and Systems Thinking, by Karl Scotland
  19. 19. Become More Agile More or less Not either/ or img:
  20. 20. Tech Debt vs Quality Legacy Maintenance Unpredictabilityill.: Jørn Ola Birkeland, XP2010: From a timebox tangle to a more flexible flow
  21. 21. Improve Quality Kanban 201 ill.: Jørn Ola Birkeland, XP2010: From a timebox tangle to a more flexible flow
  22. 22. Enable and Use Kanban 201Swarming, Slack 1. Can you help progress an existing kanban? Work on that. 2. Don’t have the right skills? Find bottleneck and work to release it. (SWARMING) 3. Don’t have the right skills? Do work which - won’t create any work downstream, - will improve future throughput and - can be paused as soon as existing kanban related work is available. (SLACK)
  23. 23. Cumulative Flow DiagramMetrics Sources of Error Some work off the board Work items vary too much in sizeill.: Henrik Kniberg & Mattias Skarin: Kanban and Scrum - making the most of both
  24. 24. ResourcesDavid Anderson: Kanbanhttp://agilemanagement.netHenrik Kniberg One day in Kanban landLinks in slides, particularly:Karl Scotland (articles)Jørn Ola Birkeland (video)