The document outlines the principles of Lean Software Development, emphasizing the importance of delivering customer value efficiently by minimizing waste. It presents key practices such as eliminating waste, amplifying learning, and empowering teams to enhance workflow and productivity. Additionally, it provides actionable steps for both individuals and teams to implement Lean strategies effectively.

1. 11K
@ahab1972© Andreas Hägglund 11K
Andreas Hägglund
I run projects and make organizations more efficient
Get Started With
Lean Software Development
11K
slideshare.net/andreashagglund
@ahab1972
andreashagglund
ah@11k.se

2. 11K
@ahab1972© Andreas Hägglund 11K
Get started with
Lean Software Development
platinum sponsor
gold sponsor
silver sponsors
bronze sponsors
11K

3. 11K
@ahab1972© Andreas Hägglund 11K© Andreas Hägglund 11K
Lean & Agile Origins
1990 1996 2003

4. 11K
@ahab1972© Andreas Hägglund 11K
Lean Management
Lean is about quickly deliver customer value
from concept to cash, by minimizing waste.
Shigeo Shingo: “It’s only the last turn of
the bolt that tightens it – the rest is just
movement”

5. 11K
@ahab1972© Andreas Hägglund 11K
Optimize the Whole
Principles of Lean Management
1. Create Long Term Business Value
2. Continuous Learning / Improvements
3. Reduce Waste
4. Increase Flow
5. Respect
Respect
ReduceWaste
IncreaseFlow
Continous
Improvemenet
Value
“A bad system will beat a
good person every time”
- W. Edwards Deming

6. 11K
@ahab1972© Andreas Hägglund 11K
1. Eliminate Waste
2. Amplify Learning
3. Decide as Late as Possible
4. Deliver as Fast as Possible
5. Empower the Team
6. Build Integrity In
7. See the Whole
Lean Software Development

7. 11K
@ahab1972© Andreas Hägglund 11K
1 – Eliminate Waste (uselessness)
1. Defects
2. Overproduction – Extra Features
3. Transportation - Handoffs
4. Waiting - Delays
5. Inventory - WIP
6. Motion – Task Switching
7. Processing – Unneeded Processes
(8. Unused Talent/Skill)
11K

8. 11K
@ahab1972© Andreas Hägglund 11K
Don’t build
features
that nobody
needs right
now
Don’t write
more spec
than you
can code
Don’t write
more code
than you
can test
Don’t test
more code
than you
can deploy
4 Simple Ways of Reducing Waste

9. 11K
@ahab1972© Andreas Hägglund 11K

10. 11K
@ahab1972© Andreas Hägglund 11K
1. Visualize the Workflow
2. Limit Work-in-Progress (WIP)
3. Measure and Manage Flow
4. Make Process Policies Explicit
5. Use Models to Evaluate Improvement
Opportunities
“Pull” Reduces WIP & Delays

11. 11K
@ahab1972© Andreas Hägglund 11K
Continous Improvement
Waiting
Extra Features
Wrong Features
Paperwork
Bugs
Work In Progress
Task Switching

12. 11K
@ahab1972© Andreas Hägglund 11K
See the waste...
Suggest
feature
Specify
feature
Develop
feature
Test
feature
Deploy
feature
Use/pay
feature

13. 11K
@ahab1972© Andreas Hägglund 11K
... And eliminate it!
See the waste...
Suggest
feature
Specify
feature
Develop
feature
Test
feature
Deploy
feature
Use/pay
feature

14. 11K
@ahab1972© Andreas Hägglund 11K
... And eliminate it!
See the waste...
Suggest
feature
Specify
feature
Develop
feature
Test
feature
Deploy
feature
Use/pay
feature
1hour
120hours
16hours
24hours
16hours
40hours
4hours
24hours
1hour
24hours

15. 11K
@ahab1972© Andreas Hägglund 11K
... And eliminate it!
But also minimize unevenness and overburden
See the waste...
Suggest
feature
Specify
feature
Develop
feature
Test
feature
Deploy
feature
Use/pay
feature
1hour
120hours
16hours
24hours
16hours
40hours
4hours
24hours
1hour
24hours
38 hours
232 hours
----------------
16% Efficiency

16. 11K
@ahab1972© Andreas Hägglund 11K
2 - Amplify Learning

17. 11K
@ahab1972© Andreas Hägglund 11K
Information Radiators Visualizes Work

18. 11K
@ahab1972© Andreas Hägglund 11K
If you could have only one information radiator;
1. What would it show?
2. Where would you put it?
3. When would you study it?
Radiators Increases learnings
Todo Dev Test Done

19. 11K
@ahab1972© Andreas Hägglund 11K
Do you need to set the entire architecture upfront?
Do you need to decide on all the requirements?
What do you really, really need to decide up front?
3 - Decide As Late As Possible

20. 11K
@ahab1972© Andreas Hägglund 11K
1 person doing
Task Switching
4 – Deliver As Fast As Possible
4 people focusing
on 4 different things
4 people focusing
on 1 thing

21. 11K
@ahab1972© Andreas Hägglund 11K
Work in Progress Through-Put

22. 11K
@ahab1972© Andreas Hägglund 11K
Through-Put ROI
Time
Cashflow
1st Release
Investment
Payback
Profit
Loss

23. 11K
@ahab1972© Andreas Hägglund 11K
5 - Empower the Team

24. 11K
@ahab1972© Andreas Hägglund 11K
No One Ever Washes a Rented Car

25. 11K
@ahab1972© Andreas Hägglund 11K
6 - Build Integrity In
0% Flaws
0% Defects
0% Decay
Simplicity
Fast Feedback
Refactoring
Testing

26. 11K
@ahab1972© Andreas Hägglund 11K
7 - See The Whole
5 Why

27. 11K
@ahab1972© Andreas Hägglund 11K© Andreas Hägglund 11K
How To Get Started
Personal Level
1. Do the Gemba Walk
2. Limit Personal WIP
3. Visualize Work
4. Ask the 5 Why
5. Take time to reflect on
your process
Team Level
1. Map the value stream
2. Eliminate delays
3. Eliminate bottlenecks
4. Limit team WIP
5. Get your own car!

28. 11K
@ahab1972© Andreas Hägglund 11K
1. Map your project stream, from idea to usage
2. List work time + idle time
3. Calculate Cycle Efficiency
4. Identify ways of increasing efficiency
Value Stream Mapping
Suggest
feature
Specify
feature
Develop
feature
Test
feature
Deploy
feature
Use/pay
feature
1hour
120hours
16hours
24hours
16hours
40hours
4hours
24hours
1hour
24hours
38 hours
232 hours
----------------
16% Efficiency

29. 11K
@ahab1972© Andreas Hägglund 11K
Thank you
11K
slideshare.net/andreashagglund
@ahab1972
andreashagglund
ah@11k.se

30. 11K
@ahab1972© Andreas Hägglund 11K
Andon – Signaling System
Kanban – Sign/card
Jidoka – Autonomation (detecting
abnormalities)
Kaizen - (continuous) change for
better
Muda – Uselessness (7 wastes)
Mura – Uneveness/irregularity
Muri – Overburden
Genba – The real place
Lean Dictionary