Kanban for SCRUMmers By Ilan Kirschenbaum @ AgileIL12

2. Do we really
need to
change?

3. Ilan Kirschenbaum
Agile coach at Practical Agile
Find me at:
http://practical-agile.com
http://fostnope.com
at Wordpress.com
Twitter: kirschi_
Facebook: Ilan Kirschenbaum

17. Now tell us
something we
don’t know

24. Quality, Cost, Lead Time, Morale, Safety
Respect for People
In-station
Just In Time Continuous
Quality
Pull, Flow Improvement (Kaizen)
(Jidoka)
Reduce Waste
Stability, Standardization, Leveling (heijunka)

25. Choose the project
Map your current process
Find and reduce waste
Identify and respect WIP limits
Maintain Flow by Pulling work
Continuously Improve

26. Lead Time
Costs
Value adding and essential waste
Non-essential waste

29. Waste = Investing in efforts that do not
contribute to value
Partially done work
Extra features
Rework
Redundant handoffs
Delays
Context switching
Defects
Ignoring creativity

30. Value adding work
Activities that directly contribute to
working product
Essential waste
Activities that the customer will not pay
for, but are unavoidable
Non essential waste
Activities that the customer will not pay
for, and can be eliminated or reduced

32. Which Side of This Road Would You Rather Drive?

35. Redefining the daily meeting
Does the Kanban reflect our activity?
Is there anything blocking us?
Are we blocking anyone?

36. Yes – if you need it
Define your Cadence, and create the
rhythm of
Planning
Reviewing
Retrospection

37. 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 rate
Match your measure to your goals

38. Backlog
WIP
Avg Cycle Time
Avg Lead Time
Source: Target Process

39. Source: Target Process

40. Source: Attlasian

41. Source: Sonar

42. What’s Next?

46. So, Do we
really need to
change?

48. If it ain’t broken – don’t fix it
If it is broken, use what you already
know to fix it
If 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

50. Salmon: http://www.flickr.com/photos/66143381@N07/6106820290/
Ruins: http://www.flickr.com/photos/blathlean/5424392859/
Daily SCRUM http://www.flickr.com/photos/improveit/1470213411/
Yawn http://www.flickr.com/photos/melissadion/4480984908/
Kanban – Karl Scotland http://agile.dzone.com/news/introducing-kanban-flow-and
Toyota http://www.flickr.com/photos/katerha/5581762999/
Piggly Wiggly http://www.flickr.com/photos/pixelpackr/91923434/
JIT – Dilbert, Scott Adams. Found at http://www.witiger.com/internationalbusiness/JIT.htm
Customer service http://www.socialsellingu.com/blog/5-reasons-add-customer-satisfaction-survey
Value Stream Mapping – Courtesy of Amdocs
WIP – Henrik Kniberg
CFD – Target Process http://www.targetprocess.com/blog/2010/02/cumulative-flow-chart-in-kanban-real-usage-
example.html
Cycle time – Target Process http://www.targetprocess.com/userguides/userguide.html
Defects – created vs. resolved: Atlassian
https://confluence.atlassian.com/display/JIRA/Created+vs+Resolved+Issues+Report
Code coverage: Sonar http://www.sonarsource.org/sonar-to-manage-unit-tests-and-improve-code-coverage/
Kanban big to small – Joseph Wilk http://agilepractitioners2012.com/wp-content/uploads/2011/11/Joe-Wilk-
Testing-In-the-land-of-Startups.pdf
Toyota Production System http://en.wikipedia.org/wiki/Toyota_Production_System
The Toyota Way http://en.wikipedia.org/wiki/The_Toyota_Way
The Machine That Changed the World by by James P. Womack, Daniel T. Jones (scientist), and Daniel Roos
Stopwatch http://www.flickr.com/photos/rsdio/3642425935/
Dollar http://www.flickr.com/photos/8011986@N02/2965137520/
Traffic http://www.flickr.com/photos/stevenworster/6122957783/