introduction to lean software development
DESCRIPTION
Introduction to lean software development for scrum audienceTRANSCRIPT
2
About me:
• EVP R&D @ GigaSpaces Technologies
• Using Scrum for 5+ years
• Background in Software Architecture/Development/Management
• Contact– [email protected]
3
About GigaSpaces
2008 Federal Reserve System Developers Conference
• >100 direct customers, 2000+ deployments• Unique position as the leading Cloud Application Server
Objectives
• Taste Lean Software Development principles in 45 minutes
• Differences and similarities between scrum and lean
Origins of Lean Thinking
1908 - Model T 1915 - 500,000 T, 50% increase per year1965 - 2,000,0001980 - Japan intruded, Quality revolution started2006 - 12.7 B lost
1930 - founded1950 - Ohno invented TPS1991 - The whole world learnt from Toyota2006 - passed Ford2007 - passed GM and world’s largest2007 - earned 15.7 B2008 - renamed Toyota Corporation; 45 of 50 Industrial classification
Principles of Lean Thinking
• Value - Specify the value desired by the customer
• Eliminate Waste - Identify the value stream for each product providing that value and challenge all of the wasted steps (generally nine out of ten) currently necessary to provide it
• Continuous Flow - Make the product flow continuously through the remaining, value-added steps
• Pull - Introduce pull between all steps where continuous flow is possible
• Pursue Perfection - Manage toward perfection so that the number of steps and the amount of time and information needed to serve the customer continually falls
Lean Software Development
Principles of Lean Thinking
1. Eliminate Waste2. Increase Feedback3. Delay Commitment4. Deliver Fast5. Build Integrity In6. Empower the Team7. See the Whole
IdentifyValue
Stream
Flow
Customer
Pull
PursuePerfecti
on
SpecifyValue
How is lean different?
Examples:1. Sprint without product release2. Manual work3. Integrations4. Specifications5. Buffers
“Can’t release every 4 weeks” – let’s increase iteration length!
The famous ‘overheads’
Solution:1. Understand ‘Why’ – what is the
root cause2. Eliminate!
Eliminate Waste
The seven (+1) wastes
• Partially Done Work• Extra Processes• Extra Features• Task Switching• Waiting• Motion• Defects• Unused Employee Creativity
Deliver as fast as possible
Kanban
Todo In Progress
Done
Item 1
Item 2
Item 3
Item 4
Kanban
Todo In Progress
Done
Item 1
Item 2Item 3
Item 4
Kanban
Todo In Progress
Done
Item 1Item 2
Item 3
Item 4
Item 6
Item 5
Monitor WIP
Kanban
Information Radiators
• Visualize the Workflow• Self Organizing Teams– Empower the workers– Accountability
• Stop the line culture
Build Integrity In
• Perceived Integrity– Users ‘love’ the product– Emotional reaction
• Conceptual Integrity
Lean vs. Scrum
• Why– Lean is the
resonating• What and How– Scrum is a
detailed recipe