Applying Lean Thinking to Software Development

Post on 21-Oct-2014

369 views 3 download

Tags:

description

Discover improvement potential in the places you might not expect it

Transcript of Applying Lean Thinking to Software Development

to Software DevelopmentApplying Lean Thinking

Sunday 27 October 13

Who Am I?

Steven PeetersFreelance team and process manager at Silver Lining bvba

๏ 15+ years of software development๏ User Group Manager๏ Adobe Community Professional๏ Lean Six Sigma Black Belt

Email: steven@silver-lining.beTwitter: @aikisteveWebsite: www.silver-lining.be

Sunday 27 October 13

Sunday 27 October 13

What is Lean IT?

Sunday 27 October 13

What is Lean IT?

The right information

Sunday 27 October 13

What is Lean IT?

The right informationAt the right time

Sunday 27 October 13

What is Lean IT?

The right informationAt the right timeIn the right format

Sunday 27 October 13

What is Lean IT?

The right informationAt the right timeIn the right formatTo the right people

Sunday 27 October 13

Why Lean IT?

“If you feel like you have everything under control, you’re just not going fast enough”

Mario Andretti - F1 world champion 1978

Sunday 27 October 13

Lean Concepts

KanbanValue Stream MappingPull systemCOPQThe 7 wastes of ITRhythm wheels

Sunday 27 October 13

Kanban

Sunday 27 October 13

Kanban

Scrum-boardVisual ManagementTracking and overview purposesLots of tools available, both real-life and virtual

๏ JIRA (GreenHopper)๏ LeanKit๏ Topdesk๏ Mantis๏ Bugzilla๏ ...

Sunday 27 October 13

Kanban

Sunday 27 October 13

Value Stream Mapping

Sunday 27 October 13

Value Stream Mapping

Look at process cycle efficiency (PCE)

Sunday 27 October 13

Value Stream Mapping

Look at process cycle efficiency (PCE)Value-add vs non-value-add vs business-value-add

Sunday 27 October 13

Value Stream Mapping

Look at process cycle efficiency (PCE)Value-add vs non-value-add vs business-value-addDetect bottlenecks

Sunday 27 October 13

Value Stream Mapping

Look at process cycle efficiency (PCE)Value-add vs non-value-add vs business-value-addDetect bottlenecksEliminate duplicates, distribute responsibilities, remove excess processing

Sunday 27 October 13

Value Stream Mapping

Look at process cycle efficiency (PCE)Value-add vs non-value-add vs business-value-addDetect bottlenecksEliminate duplicates, distribute responsibilities, remove excess processing Eliminate waste and increase flow

Sunday 27 October 13

Value Stream Mapping

Sunday 27 October 13

Value Stream Mapping

Sunday 27 October 13

Pull System

Little’s Law

WIP PLT =

PCE

Sunday 27 October 13

COPQ

Sunday 27 October 13

COPQ

Cost Of Poor Quality

Sunday 27 October 13

COPQ

Cost Of Poor QualityCost that would disappear if products, processes and systems were perfect

Sunday 27 October 13

COPQ

Cost Of Poor QualityCost that would disappear if products, processes and systems were perfectAdditional cost of non-value added time

Sunday 27 October 13

COPQ

Cost Of Poor QualityCost that would disappear if products, processes and systems were perfectAdditional cost of non-value added time“The hidden factory”

Sunday 27 October 13

COPQ in IT

Sunday 27 October 13

COPQ in IT

Bug fixes

Sunday 27 October 13

COPQ in IT

Bug fixesCode read failures

Sunday 27 October 13

COPQ in IT

Bug fixesCode read failuresIncorrect intake or bug report

Sunday 27 October 13

COPQ in IT

Bug fixesCode read failuresIncorrect intake or bug reportScope creep

Sunday 27 October 13

COPQ in IT

Bug fixesCode read failuresIncorrect intake or bug reportScope creepNo documentation

Sunday 27 October 13

COPQ in IT

Bug fixesCode read failuresIncorrect intake or bug reportScope creepNo documentationPoorly trained developers

Sunday 27 October 13

COPQ in IT

Bug fixesCode read failuresIncorrect intake or bug reportScope creepNo documentationPoorly trained developersA lot of backlog

Sunday 27 October 13

COPQ in IT

Bug fixesCode read failuresIncorrect intake or bug reportScope creepNo documentationPoorly trained developersA lot of backlogExcessive quality controls

Sunday 27 October 13

COPQ in IT

Bug fixesCode read failuresIncorrect intake or bug reportScope creepNo documentationPoorly trained developersA lot of backlogExcessive quality controls...

Sunday 27 October 13

The 7 wastes of IT

TIMWOOD

Sunday 27 October 13

The 7 wastes of IT

TIMWOOD

ransport

Sunday 27 October 13

The 7 wastes of IT

TIMWOOD

ransportnventory

Sunday 27 October 13

The 7 wastes of IT

TIMWOOD

ransportnventoryotion

Sunday 27 October 13

The 7 wastes of IT

TIMWOOD

ransportnventoryotionaiting

Sunday 27 October 13

The 7 wastes of IT

TIMWOOD

ransportnventoryotionaitingver-production

Sunday 27 October 13

The 7 wastes of IT

TIMWOOD

ransportnventoryotionaitingver-productionver-processing

Sunday 27 October 13

The 7 wastes of IT

TIMWOOD

ransportnventoryotionaitingver-productionver-processingefects

Sunday 27 October 13

The 7 wastes: Transport

Usually not physicalDocument hand-offSystems interchangeIntroduces wait time !Introduces setup time !

Sunday 27 October 13

The 7 wastes: Inventory

Backlog“Stock” building upBad task systemCan be introduced by the other 6 wastes

Sunday 27 October 13

The 7 wastes: Motion

Physical motionPeople or objects moving aboutPutting people physically in the same roomProximity of the scrum boardExcessive keystrokes in software

Sunday 27 October 13

The 7 wastes: Waiting

Non-value-added timeSystem downtimeWaiting for approvalsBuild up inventoryIncrease setup time

Sunday 27 October 13

The 7 wastes: Over-production

Scope creepEver changing requirementsSpending too much time80/20 rule

Sunday 27 October 13

The 7 wastes: Over-processing

Sunday 27 October 13

The 7 wastes: Over-processing

Complicated process flowBuilding complex solutions for simple thingsToo many control stepsOverlapping tasks and responsibilities“Red tape”

Sunday 27 October 13

The 7 wastes: Defects

Bug reportsScope not deliveredTest failuresBad intake

Sunday 27 October 13

Rhythm Wheels in IT

Sunday 27 October 13

Rhythm Wheels in IT

Supply chain system

Sunday 27 October 13

Rhythm Wheels in IT

Supply chain systemWeekly rotating roles

Sunday 27 October 13

Rhythm Wheels in IT

Supply chain systemWeekly rotating rolesKnowledge transfer

Sunday 27 October 13

Rhythm Wheels in IT

Supply chain systemWeekly rotating rolesKnowledge transferReduce setup time

Sunday 27 October 13

Rhythm Wheels in IT

Sunday 27 October 13

Conclusion

Lean IT can help you make your (internal) customers happy.

It’s the customer who defines the quality of your service!

Don’t ever stop improving your process. It’s called CONTINUOUS improvement for a reason!

Sunday 27 October 13

Thank You !

steven@silver-lining.be

@aikisteve

www.silver-lining.be

Sunday 27 October 13