SPEED QUALITY LOW COST

1
Lean Software Development

• SPEED QUALITY LOW COST
• by
• Prasath Govindarajulu
• 
  Software Development
• CS564

2
Introduction

• Application of lean principles to develop
  software
• Think big, act small, fail fast learn rapidly
• Improves the quality of the software solutions

3
Contd..

• It follows a strategically focused methodology
  unlike agile methodologies
• Not a development methodology rather offer
  principles to improve software development

4
Seven Principles of LSD

• Eliminate waste
• Amplify learning
• Decide as late as possible
• Deliver as fast as possible
• Empower the team
• Build integrity in
• See the whole

5
Seven Wastes

• 7 Wastes of 7 wastes
  of manufacturing
• Software development
• - Partially done work -Inventory
• - paperwork
  -Processing
• - extra features
  -Overproduction
• - Task switching -Motion
• - Handoffs
  -Transportation
• - Delays
  -Waiting
• -Defects -Defects

6
Eliminate Waste

• everything not adding value to the Customer is
  considered to be waste
• In software development the wastes are,
• additional code and functionalities
• delay in the software development process
  
• unclear requirements
• slow internal communication and
• does not deliver business value to
• Tools Seeing waste, Value stream mapping

7
Amplify learning

• Programmers learn many things to develop a
  valuable system.
• Some are technical and others are requirements
  related
• Tools Feedback, Iterations, Synchronization,
  Set-based Development
• Run the testing as soon as the code is written
• Simplify the process of getting user requirements
• Increasing short feedback sessions with customer
  helps in analyzing the project.

8
Decide as late as possible

• Obtain the decision based on facts not on
  uncertain future predictions
• Delay the crucial decisions until the customers
  realize their needs better

9
Deliver as fast as possible

• The sooner the end product is delivered, the
  sooner feedback can be received, and incorporated
  into the next iteration
• Shorter the iterations the better learning and
  communications within the team
• We could apply the Just in Time ideology to
  software development

10
Empower the team

• The quality of the team is the important criteria
  for delivering the successful product
• Experienced project managers finds good people
  and lets them do their own job
• There should be developer customer interaction
• Tools Self Determination, Motivation,
  Leadership, Expertise

11
Build integrity in

• Perceived integrity - customer experience with
  the system
• Conceptual integrity
• For better integral architecture- Implement
  refactoring
• Test the integrity which meets the customer needs
  

12
See the whole

• Software is not sum of their parts, but the
  product of their interactions
• Root causes of bugs should be found and
  eliminated

13
Lean Principle

• 1. Detect every ambiguity
• Dont work-around even the smallest problem
• 2. Stop the line immediately
• Correct the immediate condition if necessary
• 3. Look for the root cause
• This has the major effect on the problem
• 4. Determine the best countermeasure
• Use many simple experiments
• 5. Make the countermeasure permanent
• Constant improvement constant change

14
The Lean Agenda

• Value
• People
• Process
• Flow
• Measurement

15
Value

• Everyone is expected to develop deep customer
  understanding by using one of the following
• Call center
• Sales tour
• Follow me home
• Value stream finds the organizations customer
  value
• Lean thinking is to drive down the risky
  inventory factors and provide the customer value
  as soon as possible

16
Roles of Chief engineer

• Responsible for Business Success
• Develops Deep Customer Understanding
• Develops the Product Concept
• Creates The High Level System Design
• Sets the Schedule
• Understands what customers will value and
  conveys this
• to the engineers making day-to-day
  tradeoffs
• Arbitrates trade-offs when necessary
• Defends the Vision

17
Leadership roles

• Marketing Leader
• Customer Understanding
• Release Planning
• Technical Leader
• System Architecture
• At a high level
• Work daily with those
• developing the details
• Technical Guidance
• Integration
• Tradeoffs

18
Contd..

• Process Leader
• Build Block Disciplines
• Iterative Development
• Visible Workspace
• Project Leader
• Funding
• Staffing
• (Scheduling)
• Tracking
• Solve Team Problems

19
Process

• The maturity of an organization is measured by
  how repeatedly executing its core processes
• We could add features in any order and can
  release the working version at the end of any
  iteration
• The above fact leads to just in time production
  practical
• Build integrity in to the processes by
  refactoring it to produce a valuable software

20
Contd..

• Validating the process through testing

21
Flow

• Cycle Time
• Average end-to-end process time
• from problem detection
• to problem solution
• Begins and ends with the customer
• Software Development Cycle Time
• The speed at which a customer need is reliably
  and repeatedly translated into deployed software.

22
Reducing the cycle time

• Even out the Arrival of Work
• Minimize the number of things in process
• Minimize the size of things in process
• Establish a Regular Cadence
• Limit Work to Capacity
• Use Pull Scheduling

23
Measurement

• Decomposition
• You get what you measure
• You cant measure everything
• Stuff falls between the cracks
• You add more measurements
• You get local sub-optimization
• Example
• Measure Cost, Schedule, Scope
• Quality Customer Satisfaction

24
Contd..

• Three Holistic Measurements
• 1. Average Cycle Time
• From Product Concept
• To First Release
• or from Feature Request
• To Feature Deployment
• or from Defect Report
• To Patch

25
Contd..

• 2. The Business Case
• PL
• ROI
• Goal of Investment
• 3. Customer Satisfaction
• All customers
• From downstream processes
• To ultimate users

26
Lean follows Agile Methodology

• Fundamentally incorporates iterations and the
  continuous feedback that it provides to
  successively refine and deliver a desired
  software system
• Team size in lean software development is
  generally small just like agile.
• It follows the process of continuous planning,
  continuous testing, continuous integration, and
  other forms of continuous evolution of both the
  project and the software.

27
Contd..

• Clients start with Lean and then move to Agile.
• Lean initiatives, focus on the core task of
  identifying and eliminating waste while driving
  key decisions outward in the development cycle.

28
References

• Darrell Norton's Blog http//codebetter.com/blogs/
  darrell.norton/pages/50341.aspx
• www.wikipedia.org
• http//www.poppendieck.com/overview.htm
• http//webapp.poly.asu.edu/jacmet/presentations/CI
  _files/2005/Introduction20to20Lean20Software20
  Development20Jacmet.pdf
• http//www.versionone.com/Resources/AgileDevelopme
  nt.asp