Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Kanban for scrummers

Kanban for SCRUMmers
By Ilan Kirschenbaum @ AgileIL12

  • Login to see the comments

  • Be the first to like this

Kanban for scrummers

  1. 1. Do we reallyneed tochange?
  2. 2. Ilan KirschenbaumAgile coach at Practical AgileFind me at: at Twitter: kirschi_ Facebook: Ilan Kirschenbaum
  3. 3. Now tell ussomething wedon’t know
  4. 4. Quality, Cost, Lead Time, Morale, Safety Respect for People In-stationJust In Time Continuous Quality Pull, Flow Improvement (Kaizen) (Jidoka) Reduce Waste Stability, Standardization, Leveling (heijunka)
  5. 5. Choose the projectMap your current processFind and reduce wasteIdentify and respect WIP limitsMaintain Flow by Pulling workContinuously Improve
  6. 6. Lead Time CostsValue adding and essential wasteNon-essential waste
  7. 7. Waste = Investing in efforts that do notcontribute to value Partially done work Extra features Rework Redundant handoffs Delays Context switching Defects Ignoring creativity
  8. 8. Value adding work Activities that directly contribute to working productEssential waste Activities that the customer will not pay for, but are unavoidableNon essential waste Activities that the customer will not pay for, and can be eliminated or reduced
  9. 9. Which Side of This Road Would You Rather Drive?
  10. 10. Redefining the daily meeting Does the Kanban reflect our activity? Is there anything blocking us? Are we blocking anyone?
  11. 11. Yes – if you need itDefine your Cadence, and create therhythm of Planning Reviewing Retrospection
  12. 12. Where does it hurt?What would you discuss in your Kaizen? Time to Market? Try CFD and Cycle Time Quality? Try Code Coverage or Defects rateMatch your measure to your goals
  13. 13. Backlog WIP Avg Cycle Time Avg Lead TimeSource: Target Process
  14. 14. Source: Target Process
  15. 15. Source: Attlasian
  16. 16. Source: Sonar
  17. 17. What’s Next?
  18. 18. So, Do wereally need tochange?
  19. 19. If it ain’t broken – don’t fix itIf it is broken, use what you alreadyknow to fix itIf it doesn’t fit – see if Kanban fits Daily releases – e.g. support, short SLA Chaotic requirements changes – e.g. Start- up Not SCRUM-able – e.g. large complex team
  20. 20. Salmon: SCRUM – Karl Scotland Wiggly – Dilbert, Scott Adams. Found at service Stream Mapping – Courtesy of AmdocsWIP – Henrik KnibergCFD – Target Process time – Target Process – created vs. resolved: Atlassian coverage: Sonar big to small – Joseph Wilk Production System Toyota Way Machine That Changed the World by by James P. Womack, Daniel T. Jones (scientist), and Daniel RoosStopwatch