Kanban for SCRUMmers

PULLING IT OFF

Kanban for SCRUMmers

Do we really need to change?

Who am I ?

Ilan KirschenbaumAgile coach at Practical AgileFind me at:

http://practical-agile.com http://fostnope.com

העץ על at Wordpress.com דובדבןTwitter: kirschi_Facebook: Ilan Kirschenbaum

So, you’ve been doing SCRUM. But…

Something smells a bit…

It’s kinda working. We have a good

But too often after iteration starts, it becomes…

For starters, we get urgent stuff.It’s ok when happens occasionally…

Site Login

Buy Item

Pay Cash

Pay Credit

Create

Custome

rBuy Service

Change

Address

Shorten

Startup

Time

But...

Site Login

Buy Item

Pay Cash

Shorten

Startup

Time

Pay CreditCreate

Custome

rBuy ServiceChange

Address

Urgent

CR

Defect

#xxxPrepare

Demo to

CEO

Build Server

dead

We use the Burn Down Chart…

Site Login

Buy Item

Pay Cash

Pay Credit

Create

Custome

rBuy Service

Change

Address

Shorten

Startup

Time

But it soon becomes…

Site Login

Buy Item

Pay Cash

Pay Credit

Create

Custome

rBuy Service

Change

Address

Shorten

Startup

Time

We do a daily SCRUM

Site Login

Buy Item

Pay Cash

Pay Credit

Create

Custome

rBuy Service

Change

Address

Shorten

Startup

Time

But it soon becomes…

Site Login

Buy Item

Pay Cash

Pay Credit

Create

Custome

rBuy Service

Change

Address

Shorten

Startup

Time

Site Login

Buy Item

Pay Cash

Pay Credit

Create

Custome

rBuy Service

Change

Address

Shorten

Startup

Time

Oh, one more thing…

SCRUM assumes we release in iterations

In fact, we have to release whenever customers need to

Kanban for SCRUMmers

Now tell us something we don’t know

Hello Kanban

How is Kanban different from SCRUM?

Buy Item

Shorten

Startup

Time

Site Login

Pay CashBuy

Service

Create

Customer

Change

Address

Pay Credit

The (not so) Small Print

The (not so) Small Print

Started in Toyota, Many Years Ago

Piggly Wiggly and Just In Time

Continuous Improvement

(Kaizen)

Evolved into Toyota Production System

Stability, Standardization, Leveling (heijunka)

Just In TimePull, Flow

In-station Quality (Jidoka)

Respect for People

Quality, Cost, Lead Time, Morale, Safety

Reduce Waste

The Path to Lean Software Development

Choose the projectMap your current processFind and reduce wasteIdentify and respect WIP limitsMaintain Flow by Pulling workContinuously Improve

Map Your Process: Value Stream Mapping

Value adding and essential waste

Non-essential waste

Lead Time

Costs

Map Your Process: Value Stream Mapping

From Value Stream Mapping to Kanban Board

Buy Item

Shorten

Startup

Time

Site Login

Pay CashBuy

Service

Create

Customer

Change

Address

Pay Credit

Find and Reduce Waste

Waste = Investing in efforts that do not contribute to value

Partially done workExtra featuresRework Redundant handoffsDelaysContext switchingDefectsIgnoring creativity

Remember – Not all Waste is Bad

Value adding workActivities that directly contribute to working product

Essential wasteActivities that the customer will not pay for, but are unavoidable

Non essential wasteActivities that the customer will not pay for, and can be eliminated or reduced

Setting Work In Progress (WIP) Limits

Buy Item

Shorten

Startup

Time

Site Login

Pay CashBuy

Service

Create

Customer

Change

Address

Pay Credit

223

Limit Work In Progress to CapacityWhich Side of This Road Would You Rather Drive?

Flow & Pull

Buy Item

Shorten

Startup

Time

Site Login

Pay CashBuy

Service

Create

Customer

Change

Address

Pay Credit

223

Flow & Pull

Flow & Pull

Redefining the daily meetingDoes the Kanban reflect our activity?Is there anything blocking us?Are we blocking anyone?

No Planning?! No Review?!

Yes – if you need itDefine your Cadence, and create the rhythm of

PlanningReviewingRetrospection

Improve it – OPS Review

Where does it hurt? What would you discuss in your Kaizen?

Time to Market? Try CFD and Cycle TimeQuality? Try Code Coverage or Defects rate

Match your measure to your goals

Visualizing the Process – Cumulative Flow Diagram

Avg Cycle Time

WIP

Backlog

Avg Lead Time

Source: Target Process

Visualizing the Process – Cycle Time

Source: Target Process

Visualizing the Process – Created vs. Resolved defects

Source: Attlasian

Visualizing the Process – Code Coverage

Source: Sonar

Kanban for SCRUMmers

What’s Next?

Class of Service with Swimlanes

Buy Item

Shorten

Startup

Time

Site Login

Pay Cash

Buy Service

Create

Customer

Change

Address

Pay Credit

UBUNTU

Support

Refactor

Login token

Urgent CRDemo to

CEO

SCRUM-BAN

Buy Item

Shorten

Startup

Time

Site Login

Pay Cash

Buy Service

Create

Customer

Change

Address

Pay Credit

Refactor

Login token

Urgent CR Demo to

CEO

Custome

r

Security

SCRUM-BAN, Another Option

Buy Item

Shorten

Startup

Time

Site Login

Pay CashBuy

Service

Create

Customer

Change

Address

Pay Credit

UBUNTU

Support

Refactor

Login token

Urgent CRDemo to

CEO

Kanban for SCRUMmers

So, Do we really need to change?

More is not always Good

Kanban for SCRUMmers

If it ain’t broken – don’t fix itIf it is broken, use what you already know to fix itIf it doesn’t fit – see if Kanban fits

Daily releases – e.g. support, short SLAChaotic requirements changes – e.g. Start-upNot SCRUM-able – e.g. large complex team

Kanban for SCRUMmers

PULLING IT OFF

Credits and ReferencesSalmon: 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-andToyota 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 AmdocsWIP – Henrik KnibergCFD – Target Process http://www.targetprocess.com/blog/2010/02/cumulative-flow-chart-in-kanban-real-usage-example.htmlCycle 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.pdfToyota Production System http://en.wikipedia.org/wiki/Toyota_Production_SystemThe Toyota Way http://en.wikipedia.org/wiki/The_Toyota_WayThe Machine That Changed the World by by James P. Womack, Daniel T. Jones (scientist), and Daniel RoosStopwatch http://www.flickr.com/photos/rsdio/3642425935/Dollar http://www.flickr.com/photos/8011986@N02/2965137520 / Traffic http://www.flickr.com/photos/stevenworster/6122957783/