This document discusses Lean Software Development. It begins with a brief history of Lean, noting its origins in manufacturing and its application to software development starting in the 1990s. It then defines Lean according to the five pillars of Lean thinking: value, value stream, flow, pull, and perfection. The document outlines six Lean values related to accepting human factors and complexity while striving for better economic and social outcomes. It also lists seven Lean principles for software development, such as eliminating waste, building quality in, and respecting people. The document provides examples of Lean practices and concludes that Lean is a methodology for trimming non-value-added activities from the software development process while following any development methodology.

1. Lean Software Development
Values and Principles
Balaji Sathram, PMI-ACP, CSP, CSM.
15th May 2015.

2. Agenda
• Lean-History
• Lean-Definition
• Lean-Values
• Lean-Principles
• Activity
• Lean Practices
• Conclusion
2

3. Lean - History
• 1988: The term “Lean” was first coined by John Krafcik in his article, "Triumph of the Lean
Production System“.
• 1991: Word “Lean” was mentioned in the book “The Machine That Changed the World:
the Story of Lean Production” by James Womack, Daniel Jones, and Daniel Roos as a
term to describe the Toyota management approach.
• 1992: The term Lean Software Development was first coined as the title for a conference
organized by European Union in Stuttgart, Germany.
• 1993: Robert “Bob” Charette explored better ways of risk management in software
projects and suggested the concept of “Lean Software Development”
• 1995: Five pillars of Lean thinking are defined in the book titled “Lean Thinking: Banish
Waste and Create Wealth in your Corporation” by Womack, James P and Daniel T. Jones
3

4. Lean-Definition
Muda – literally meaning “waste” but implying non-value-added activity
Mura – meaning “unevenness” and interpreted as “variability in flow”
Muri – meaning “overburdening” or “unreasonableness”
• Five pillars of Lean thinking are value, value stream, flow, pull
and perfection. These pillars have become the working definition
of Lean. People started identifying & eliminating waste activities
(non-value-added activity) in the workflow to reach perfection.
• Eliminating waste is an exclusive property/practice of Lean till
date.
• Womack and Jones didn’t share the definition to the world,
Toyota management principles are difficult to describe or to
analyze. The word “Waste” is described in detail with three
Japanese terms:
4

5. Lean Values
In 2011, the Lean Systems society published a set of values. Those values are
• Accept the human condition
• Accept that complexity & uncertainty are natural to knowledge work
• Work towards a better Economic Outcome
• While enabling a better Sociological Outcome
• Seek, embrace & question ideas from a wide range of disciplines
• A values-based community enhances the speed & depth of positive change
5

6. Accept
the
human
condition
6

7. Accept that complexity & uncertainty are
natural to knowledge work
7

8. Work towards a better Economic Outcome
8

9. While enabling a better Sociological Outcome
9

10. Seek, embrace & question ideas from a wide
range of disciplines
10

11. A values-based community enhances the
speed & depth of positive change
11

12. Lean Principles
There are 7 lean principles which seems to
agreed & practiced globally with most of the
software development processes
• Eliminate Waste
• Create Knowledge
• Build Quality In
• Defer Commitment
• Optimize the whole
• Deliver Fast
• Respect people
12

13. Eliminate Waste
13

14. Create Knowledge
14

15. Build Quality In
15

16. Defer Commitment
16

17. Optimize the Whole
17

18. Deliver Fast
18

19. Respect People
19

20. Activity
You and your friend has gone to a bakery to eat a cake
• List out all the activities in the process (primary flow)
• Identify alternate flows
• Identify value adding and non-value adding activities
• Provide improvement actions
• Calculate Efficiency
20

21. 21

22. Lean Practices
Apart from lean values and principles, there are quite a number of practices commonly
adopted. Some of the lean practices are mentioned below.
• Cumulative Flow Diagrams
• Visual Controls
• Virtual Kanban Systems
• Small Batch Sizes / Single-piece Flow
• Automation
• Kaizen Events
• Daily standup meetings
• Retrospectives
• Operations Reviews
22

23. Conclusion
• No hard and fast prescriptions to follow from Lean Software Development.
• Follow any of the available software development methodologies but make sure that
actual process definitions are aligned with the Lean values and principles to be lean.
• Definitely Lean is a methodology which will trim the fat from the software process
(Starting from requirements to product delivery to the customer)
23

24. Thank you
24