c



LEAN in Software ................................ ................................ ................................ ................................ ..... 2 ë





LEAN Overview ................................ ................................ ................................ ................................ 2 ë





Lean Speak ................................ ................................ ................................ ................................ ....... 2 ë





Lean Principles ................................ ................................ ................................ ................................ . 3 ë





Principle of Lean Thinking ................................ ................................ ................................ ................ 4 ë





Lean Software Development Methodology ................................ ................................ ...................... 4 ë





Lean ʹ Deployment Approach ................................ ................................ ................................ .......... 6 ë





Lean ʹ Tools and Usage ................................ ................................ ................................ .................... 7 ë





Pros and Cons of Lean Software Development................................ ................................ ................. 8 ë





Y
 ?
 

 

?
?


?
 means ?ets liminate
ll on value adds. LEAN is a philosophy that focuses on Continuous
improvement by eliminating waste so that all steps/activities add value from the Customers perspective.
?
 means ?ets liminate
ll on value adds. Lean principles have been applied to software
development only recently. In the beginning it all started with manufacturing. Of course, it wasn͛t called
Lean back then. It was the Toyota ProductionSystem or Just-in-time manufacturing.

Lean has been successfully applied to manufacturing, supply chain, product development, banking,
engineering, and much more. However, only in the last few years have the Lean principles and
techniques been applied to software development. c

 §eorganize the paragraph so
that the philosophy͛s chronological development is
explained. Like ʹ ͞it started with manufacturing.
The Lean principles have proved remarkably applicable to improving the productivity and quality of just Due to its success it is applied to supply chain and
about any endeavor. It is a way of thinking about how to deliver value to the customer quickly by finding product development, etc.,͟ Then talk about
software.
and eliminating wastes which are impedimentsto quality and productivity. It is all about eliminating
wastes, simplifying processes and speeding up deliverables. The 3 step methodology involves identifying
wastes, investigate constraints and implement solutions.

?



Defore proceeding further, let͛s familiarize with few Japanese words that we encounter in the world of
Lean. Here͛s a short primer on a few of the more commonterms:

Y
It is a visual device or Visual aid 

Y Ñ  Autonomation, which simply means automation
Y 
 - The continuous, incremental improvement of an activity to create more value with less
waste.
Y  
Means ͞Visual card͟, ͞signboard͟ or ͞billboard͟
Y á  ʹ Mistake proofing
Y ÿ  ʹ Consistency
Y  ʹ means Waste, the activities that add no value, add cost and time.
Y  ʹ Overburden
Y  Unevenness

Y
?




Modern-day Lean has settled on five principles and a wide array of practices that have been distilled
from Toyota Production System. The five-step thought process for guiding the implementation of lean
techniques is easy to remember, but not always easy to achieve:

Y  
 - Specify value from the standpoint of the end customer by product family.
Y  
  - Identify all the steps in the value stream for each product family. It involves all
steps both value added and non value added required to complete ht e product.
Y ë

Y Y
 the value-creating steps occur in tight sequence so the product will flow smoothly
toward the customer.
Y á

ʹ Pull cascades back through the value stream and ensures that nothing is made before it is
needed, thus eliminating most in-process inventory. As flow is introduced, let customers pull
value from the next upstream activity.
Y á  ʹ Strive for perfection by continually identifying and removing wastes. c

All these bullet items need to be
conveyed to the reader in three sentences ʹ first
one should say what is that you are introducing. For
YY example ʹ what is ͞Identify Value͟ mean. Second
point should mention how do a reader can achieve
this? Third ʹ give an example.
Y

Y c

It is good to make bullet item

names synchronize with the labels in the picture.




 ?




The underlying principles of eliminating waste, empowering front line workers, responding immediately
to customer request, and optimizing across the value chain are fundamental to lean thinking. When
applied to software development, these concepts provide a broad framework for improving software
development.

There are four basic principles for lean thinking which are most relevant to software development:

Y Add Nothing Dut Value (eliminate waste)

Y Centre On The People Who Add Value
Y Flow Value From Demand (Delay Commitment)
Y Optimize Across Organizations

?
 

  

Lean Software Development has seven guiding principles andis described below in detail.

Y V
   rLean has some pretty strict views on waste and below are theseven types of c

Who created these seven rules?
People can argue that they can create more such
wastes ( ) that are easily remembered by using the acronym DOTWIMP.
types. So, to convey there are only seven, we need
 to know whether it is coming from standards based
Manufacturing Software Industry organization, or is it just formulated by Infosys.

Defects Writing wrong code or functionality which leads to bugs, which

results to rework and hence additional effort

OverProduction Fulfillment of requests that will not be released to Production

soon, extra features / unnecessary functionality

Transportation Data and Information Movement/Signoff

Waiting Key resources not available Delays due to unavailability of

information to proceed

Inventory Maintenance Dacklogs, Partially Done Work, building features for

future use

Motion Ineffective prioritization of maintenance requests Unplanned

Task Switching

Over-Processing Over-processing beyond the standards required by customer

doing more reviews, unnecessary process steps.

Additional eighth waste This is often cited as an additional type of waste beyond the
original seven, and it refers to the underutilization of the
worker͛s creativity and resourcefulness

Y D

 rEach step in the development should be mistake-proof and self-inspecting.
When a defect is detected, root cause analysis needs to be done and corrected, instead of
waiting till the end of the project.

Y c 

: Do not forget the lessons you have learned. Obviously, making the same
mistakes over again or relearning how something works is a waste of time and effort. Find ways
to record your team͛s knowledge so that you can easily locate it the next time you need it. It is
generally best to store a given piece of knowledge closest to its source (commenting the code,
recording the alternatives considered during design/decisions).

Y ˜  r The best decisions are made when you have the most information available.
If you don͛t have to make a particular decision now, wait until later when you have more
knowledge and information. Dut don͛t wait too long, eitherͶlack of a decision should not hold
up other aspects of the project. Wait until the last responsible moment to make an irreversible
decision.

Y ˜
 r means developing features in small batches that are delivered to the customer
quickly, in short iterations. The completion of each such short iteration provides an opportunity
to change and reprioritize the requirements based on real feedback and use. The end result is a
product that more closely meets the real needs of the customer, while simultaneously
eliminating the tremendous amount of waste and rework created by the requirements churnͶ
truly a win-win situation.

Y § 
r means trusting them and recognizing them for their accomplishments and
actively soliciting their advice.

Y O  

r whenever you optimize a local process, you are almost always doing so at
the expense of the whole value stream. If you don͛t have control over the entire value stream,
you may be forced to sub optimize a piece of it. In general, you should always attempt to
include as much of the value stream as you can when you try to optimize a process.
?




  c

I did not understand why you are

mentioning deployment approach right after
software development methodology. I guess you
Different phases involved during deployment of Lean process wanted to mention implementation of LEAN
philosophy as per the above software development
process. If yes, please mention that clearly and also
ÎY Data Gathering correlate the terminology you use here with the
ÎY Analysis terminology already mentioned in the prior
paragraph.
ÎY Deployment/Implementation
c

Why do you need data
gathering? Explain.

c

Why do we need to do analysis?

Also, on what type of data (or something) you do
˜

 
˜

 this analysis? Explain.

Pilot project Identification

§equest Stratification

Problem analysis and ranking

Identifying improvement area

Time Trap Analysis (elapsed calendar days for every

process steps is identified)

 
˜


c

Have you elaborated this
Time Trap transformed into VSM to assess % of Value added activities to non-value added activities abbreviation prior to this usage?

Value Stream Mapping (VSM) ʹ The value stream mapping of the

current state is drawn using Visio and Kaizen points are identified.

Why Why Analysis ʹ is carried out for Kaizen points that are
identified through VSM
˜



˜



Drainstorming (the project team members came out with

solutions to the various problems identified)

Future State VSM (Future state diagrams representing an

improved process and Goals



c

Are these tools internal to
?
 
 Infosys or need to be brought from out side?

Different techniques and tools are used during the implementation phase of Lean.

c

 What is DP?

 
   á   Ñ  

Visual control system Waste §eduction Mistake Proofing Automation

Y á Y 
 Y á Y á   
 
  
    
 á  
Y ? 
    Y á  Y   
    
 

      
Y 
   
     
       
 Y á  Y á
Y   Y       
 
 

   
 
  
 
c
 ?
 



Successful adoption of Lean Software Development is dependent on a number of factors. Specific Pros
and Cons are outlined below:

á 
Y It is development-improvement strategy that can be applied to establish software development
life cycles.
Y The principles enable incremental improvement, removing process constraints and improving
cycle times.
Y It can be applied throughout the development life cycle, from business analysis to maintenance.
Y It can be used as a stepping stone to more-agile techniques, such as XP.
Y It can be used as a wider business and IT improvement program based on lean think ing.

c 
Y It is not an out-of-the-box method and needs tailoring for each environment, which required
skill and expertise.
Y It requires considerable organizational and process changes to be effective.
Y Without the correct measurement and reporting process, it can be difficult to show the true
benefits to the organization.

c

 If possible give some examples

of successes in software and failures, citing the
reasons for them.