Upload
others
View
3
Download
0
Embed Size (px)
Citation preview
Softhouse ConsultingTel: 031 760 99 [email protected] www.softhouse.se
Tom Mårdh & Magnus Siverbrant
Softhouse
Lean and Agile
Taichii Ohno
The Lean House
• Optimize the whole • Amplify learning • Empower the team • Build quality in • Decide as late as possible • Deliver as fast as possible • Eliminate waste
The 7 Lean PrinciplesValue through the eyes of the customer
• Partially done work • Extra features • Relearning • Handoffs • Multi Tasking • Delays • Defects • (Untapped potential)
7(8) Sources of Waste
Agile Manifesto
• Individuals and interactions over Processes and tools • Working software over comprehensive Documentation • Customer collaboration over contract negotiations • Responding to change over following a plantools
http://agilemanifesto.org/
Agile principles
• Satisfy the customer through early and continuous delivery of valuable software.
• Welcome changing requirements • Business people and developers must work together daily
throughout the project. • Give people the environment and support they need • Face-to-face conversation. • Working software is the primary measure of progress. • Sustainable pace • Technical excellence • Simplicity • Collaboration gives better results • Inspect and Adapt
Scrum
Both based on a new way of thinking about the problem at hand.
Cynefin
Let's be clear on one thing.
Agile/Lean does not solve your problems!
It brings your problems to the surface and has mechanisms built in to encourage you to solve
them one by one.
Your problems are there by design
What you have now is the result of your actions and decisions up until now.
We are our habits!
“The only thing harder than starting something new is stopping something old!”
Russel Ackoff
How most companies do agile
Water - Scrum - Fall
Doing or Being
There are many levels of maturity
Exersise
2 groups of 4 volunteers
The teams will get specifications for a drawing they will get 60 seconds to draw while silent
Spec
• Draw a beautiful summer meadow with blue and red flowers in green grass, some cows and birds under a shining sun.
Specs
• 10 blue flowers with 5 petals each • 5 blue flowers with 6 petals each • 13 red flowers with 6 petals each • 2 cows with 3 black spots • 1 cow with 5 black spots • 2 cows with 4 black spots • 2 birds to reside in the upper left corner • 3 birds in the middle • one sun to the right with 5 sun beams
Draw a beautiful meadow with
Our job
Vision
What we ended up building
how did we get from one to the other?
Like this
Business
Front end
UXQA
Backend
All the brilliant people working on at least one thing each and passes it downstream when done with it's part
Or like this?
All the brilliant people working on the same thing at the same time until it's done
The feedback loop is our friend
Efficiency vs Effectiveness
Effectiveness (Complex) Reaching the best possible result with a given effort
Efficiency (Obvious/Complicated) Reaching a given result with the minimal effort.
Resource efficiency vs flow efficiency
Work Elapsed calendar time
A 10h 100 days
A 15h 10 days
No way from resource to flow efficiency
Economics of iterative delivery
• Guess 3 digits (000-999) • Guess costs 1 unit per digit • Correct guess of all 3 digits gives 3000 units
• Traditional Guess all commits to guess all 3 digits at once • Iterative Guess 1 digit at a time and decides if they want
to commit to guessing the next one based on the result
https://jsfiddle.net/h31a5z3u/3/
Result (Economics of iterative delivery)
50 simulations
Win Frequence
Survival Average Money
Average Survived Iterations
Average Traditional
0,0011 15 4620 4980
Average Iterative
0,0011 49 24343 9853
Win Frequencey = How often the guess is rightSurvival = Money left after 10,000 iterations
The Answer to How is Yes!
Questions / Discussion