applying lean thinking to software development

61
to Software Development Applying Lean Thinking Sunday 27 October 13

Post on 21-Oct-2014

372 views

Category:

Business


3 download

DESCRIPTION

Discover improvement potential in the places you might not expect it

TRANSCRIPT

Page 1: Applying Lean Thinking to Software Development

to Software DevelopmentApplying Lean Thinking

Sunday 27 October 13

Page 2: Applying Lean Thinking to Software Development

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: [email protected]: @aikisteveWebsite: www.silver-lining.be

Sunday 27 October 13

Page 3: Applying Lean Thinking to Software Development

Sunday 27 October 13

Page 4: Applying Lean Thinking to Software Development

What is Lean IT?

Sunday 27 October 13

Page 5: Applying Lean Thinking to Software Development

What is Lean IT?

The right information

Sunday 27 October 13

Page 6: Applying Lean Thinking to Software Development

What is Lean IT?

The right informationAt the right time

Sunday 27 October 13

Page 7: Applying Lean Thinking to Software Development

What is Lean IT?

The right informationAt the right timeIn the right format

Sunday 27 October 13

Page 8: Applying Lean Thinking to Software Development

What is Lean IT?

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

Sunday 27 October 13

Page 9: Applying Lean Thinking to Software Development

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

Page 10: Applying Lean Thinking to Software Development

Lean Concepts

KanbanValue Stream MappingPull systemCOPQThe 7 wastes of ITRhythm wheels

Sunday 27 October 13

Page 11: Applying Lean Thinking to Software Development

Kanban

Sunday 27 October 13

Page 12: Applying Lean Thinking to Software Development

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

Page 13: Applying Lean Thinking to Software Development

Kanban

Sunday 27 October 13

Page 14: Applying Lean Thinking to Software Development

Value Stream Mapping

Sunday 27 October 13

Page 15: Applying Lean Thinking to Software Development

Value Stream Mapping

Look at process cycle efficiency (PCE)

Sunday 27 October 13

Page 16: Applying Lean Thinking to Software Development

Value Stream Mapping

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

Sunday 27 October 13

Page 17: Applying Lean Thinking to Software Development

Value Stream Mapping

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

Sunday 27 October 13

Page 18: Applying Lean Thinking to Software Development

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

Page 19: Applying Lean Thinking to Software Development

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

Page 20: Applying Lean Thinking to Software Development

Value Stream Mapping

Sunday 27 October 13

Page 21: Applying Lean Thinking to Software Development

Value Stream Mapping

Sunday 27 October 13

Page 22: Applying Lean Thinking to Software Development

Pull System

Little’s Law

WIP PLT =

PCE

Sunday 27 October 13

Page 23: Applying Lean Thinking to Software Development

COPQ

Sunday 27 October 13

Page 24: Applying Lean Thinking to Software Development

COPQ

Cost Of Poor Quality

Sunday 27 October 13

Page 25: Applying Lean Thinking to Software Development

COPQ

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

Sunday 27 October 13

Page 26: Applying Lean Thinking to Software Development

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

Page 27: Applying Lean Thinking to Software Development

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

Page 28: Applying Lean Thinking to Software Development

COPQ in IT

Sunday 27 October 13

Page 29: Applying Lean Thinking to Software Development

COPQ in IT

Bug fixes

Sunday 27 October 13

Page 30: Applying Lean Thinking to Software Development

COPQ in IT

Bug fixesCode read failures

Sunday 27 October 13

Page 31: Applying Lean Thinking to Software Development

COPQ in IT

Bug fixesCode read failuresIncorrect intake or bug report

Sunday 27 October 13

Page 32: Applying Lean Thinking to Software Development

COPQ in IT

Bug fixesCode read failuresIncorrect intake or bug reportScope creep

Sunday 27 October 13

Page 33: Applying Lean Thinking to Software Development

COPQ in IT

Bug fixesCode read failuresIncorrect intake or bug reportScope creepNo documentation

Sunday 27 October 13

Page 34: Applying Lean Thinking to Software Development

COPQ in IT

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

Sunday 27 October 13

Page 35: Applying Lean Thinking to Software Development

COPQ in IT

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

Sunday 27 October 13

Page 36: Applying Lean Thinking to Software Development

COPQ in IT

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

Sunday 27 October 13

Page 37: Applying Lean Thinking to Software Development

COPQ in IT

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

Sunday 27 October 13

Page 38: Applying Lean Thinking to Software Development

The 7 wastes of IT

TIMWOOD

Sunday 27 October 13

Page 39: Applying Lean Thinking to Software Development

The 7 wastes of IT

TIMWOOD

ransport

Sunday 27 October 13

Page 40: Applying Lean Thinking to Software Development

The 7 wastes of IT

TIMWOOD

ransportnventory

Sunday 27 October 13

Page 41: Applying Lean Thinking to Software Development

The 7 wastes of IT

TIMWOOD

ransportnventoryotion

Sunday 27 October 13

Page 42: Applying Lean Thinking to Software Development

The 7 wastes of IT

TIMWOOD

ransportnventoryotionaiting

Sunday 27 October 13

Page 43: Applying Lean Thinking to Software Development

The 7 wastes of IT

TIMWOOD

ransportnventoryotionaitingver-production

Sunday 27 October 13

Page 44: Applying Lean Thinking to Software Development

The 7 wastes of IT

TIMWOOD

ransportnventoryotionaitingver-productionver-processing

Sunday 27 October 13

Page 45: Applying Lean Thinking to Software Development

The 7 wastes of IT

TIMWOOD

ransportnventoryotionaitingver-productionver-processingefects

Sunday 27 October 13

Page 46: Applying Lean Thinking to Software Development

The 7 wastes: Transport

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

Sunday 27 October 13

Page 47: Applying Lean Thinking to Software Development

The 7 wastes: Inventory

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

Sunday 27 October 13

Page 48: Applying Lean Thinking to Software Development

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

Page 49: Applying Lean Thinking to Software Development

The 7 wastes: Waiting

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

Sunday 27 October 13

Page 50: Applying Lean Thinking to Software Development

The 7 wastes: Over-production

Scope creepEver changing requirementsSpending too much time80/20 rule

Sunday 27 October 13

Page 51: Applying Lean Thinking to Software Development

The 7 wastes: Over-processing

Sunday 27 October 13

Page 52: Applying Lean Thinking to Software Development

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

Page 53: Applying Lean Thinking to Software Development

The 7 wastes: Defects

Bug reportsScope not deliveredTest failuresBad intake

Sunday 27 October 13

Page 54: Applying Lean Thinking to Software Development

Rhythm Wheels in IT

Sunday 27 October 13

Page 55: Applying Lean Thinking to Software Development

Rhythm Wheels in IT

Supply chain system

Sunday 27 October 13

Page 56: Applying Lean Thinking to Software Development

Rhythm Wheels in IT

Supply chain systemWeekly rotating roles

Sunday 27 October 13

Page 57: Applying Lean Thinking to Software Development

Rhythm Wheels in IT

Supply chain systemWeekly rotating rolesKnowledge transfer

Sunday 27 October 13

Page 58: Applying Lean Thinking to Software Development

Rhythm Wheels in IT

Supply chain systemWeekly rotating rolesKnowledge transferReduce setup time

Sunday 27 October 13

Page 59: Applying Lean Thinking to Software Development

Rhythm Wheels in IT

Sunday 27 October 13

Page 60: Applying Lean Thinking to Software Development

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