Flow Efficiency

© 2013 Proyectalis Gestión de Proyectos S.L. More at http://Slideshare.net/proyectalis

Flow EfficienyEurolab - Aachen, Sept. 2013


Angel Medinilla

Let’s make a couple

of changes here!

[email protected]/en/AngelMedinilla(Slides, Videos, Newsletter, Books, Blog, LinkedIn, Sketchnotes, Twitter...)

Twitter: @angel_m (would love some instant feedback!)


My Pleasure!


“Flow”


Team “Flow”

Coding

Meeting!

Coding Coding Coding Coding

Need resource! Urgent need! NeedInfo

Distracted


Team “Flow”

Coding

Meeting!

Coding Coding Coding Coding

Need resource! Urgent need! NeedInfo

Distracted

Snap! Snap! Snap!Snap!

Snap!


Team “Flow”

Coding

Meeting!

CodingCoding Coding Coding

Need resource!

Urgent need! NeedInfo

Distracted


Team “Flow”

Coding

Meeting!


Need resource!


Distracted

40% Efficiency


Team “Flow”

Coding

Meeting!


Need resource!


Distracted

40% Efficiency

(reduce another 20-40% if you are context-switching)


Team “Flow”

Week 1 Week 2 Week 3 Week 4

WIP: 1Time to market (MVP): 1 week

Cycle Time: 1 weekLead Time: 2.5 weeks


Team “Flow”

Week 4

WIP: 4Time to market (MVP): 4 weeks

Cycle Time: 4 weeksLead Time: 4 weeks

(+ context switching delay)


“Busyness”


(let’s go back to “Flow”)


KaizenKaizen


Maximize ValueOptimize Stream

Kaizen

Flow

KaizenKaizen

Pull


Maximize ValueOptimize Stream

Kaizen

Flow

KaizenKaizen

Pull

Long Term Thinking Inspect and Adapt

Develop & EmpowerRight Process

Leadership & Culture Go & See

Teamwork

See the wholeEliminate Waste

Consensus & Fast action


Value & Waste


Value Stream Map


Real Exercise - VSM + Lead Time


Scrum

“Waterfallity Rate”


Optimize Value Stream: Theory of Constraints


“One Piece Flow”


Batch Producing vs. One Piece FlowB B B B B

B B B B C C C C

3 min. 12 min.

10 min 10 min 10 min

- “Produce one, deliver one” (zero inventory)- Continuous Integration / Continuous Delivery

Little’s Law: Cycle time grows with the amount of items being processed ( L = λW, number of customer = arrival rate x average time spent)

Cycle Time = Lead Time = 30 minutes)

Cycle Tyme = 3 minutes; Lead Time = 12 minutes;


Silos & flow - SuboptimizationSelected Backlog

Code Test Done!

Design

Rdy Rdy On On


Dissatisfaction!


Did he say “continuous delivery”?


Single Minute Exchange of Die (SMED)


Single Minute Exchange of Die (SMED)

36 hours --> 10 Hours ---> 10 Minutes!

3 months --> 25 Days ---> 10 hours???


WikiSpeed


2011 !!!


The Agile Fluency Model


Wrap Up!1) Protect Developer Flow - avoid Context Switching2) Maximize value by erradicating waste3) Map and optimize the Value Stream; watch your waterfallity rate4) Help your system flow - work on small batches, deliver continuously, reduce both cycle time AND lead time6) Develop your SMED in order to make the system flow7) Progress in your Agile Fluency8) Think BEYOND!


Thank you and... BLOG IT!!

(Oh, yes, and buy the book!)http://www.proyectalis.com/en/AngelMedinilla


http://creativecommons.org/licenses/by-nc-nd/3.0/

This presentation is based upon the ideas and work of many people. And while I’ve tried to recognize copyrights and give credit and attribution where possible, I cannot possibly list them all, so if you feel like there’s something that should be added, changed or removed from this presentation, please drop me an e-mail at [email protected]

Flow Efficiency

Business

Transcript of Flow Efficiency