This document discusses lean software development principles. It begins with background on the origins of lean thinking in Toyota's production model and principles like eliminating waste, continuous flow, and pursuing perfection. Lean software development aims to eliminate waste, increase feedback, delay commitment, deliver fast, build integrity in, empower teams, and see the whole system. Examples of waste in software include partially done work, extra processes, extra features, and task switching. Kanban and information radiators are discussed as ways to visualize workflow. Lean focuses more on fundamentals like why while Scrum provides more detailed practices, but both aim to optimize value delivery.

1. Lean Software Development Guy Nirpaz, EVP R&D, GigaSpaces Technologies guy.nirpaz@gmail.com

2. 2 About me: EVP R&D @ GigaSpaces Technologies Using Scrum for 5+ years Background in Software Architecture/Development/Management Contact guy.nirpaz@gmail.com

4. Unique position as the leading Cloud Application Server2008 Federal Reserve System Developers Conference

5. Objectives Taste Lean Software Development principles in 45 minutes Differences and similarities between scrum and lean

6. Origins of Lean Thinking 1908 - Model T 1915 - 500,000 T, 50% increase per year 1965 - 2,000,000 1980 - Japan intruded, Quality revolution started 2006 - 12.7 B lost 1930 - founded 1950 - Ohno invented TPS 1991 - The whole world learnt from Toyota 2006 - passed Ford 2007 - passed GM and world’s largest 2007 - earned 15.7 B 2008 - renamed Toyota Corporation; 45 of 50 Industrial classification

8. 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

9. Lean Software Development

10. Principlesof Lean Thinking 1. Eliminate Waste 2. Increase Feedback 3. Delay Commitment 4. Deliver Fast 5. Build Integrity In 6. Empower the Team 7. See the Whole

11. How is lean different?

12. Examples: Sprint without product release Manual work Integrations Specifications Buffers

13. “Can’t release every 4 weeks” – let’s increase iteration length! The famous ‘overheads’

14. Solution: Understand ‘Why’ – what is the root cause Eliminate!

15. Eliminate Waste

16. The seven (+1) wastes Partially Done Work Extra Processes Extra Features Task Switching Waiting Motion Defects Unused Employee Creativity

17. Deliver as fast as possible

20. Kanban Todo In Progress Done Item 1 Item 2 Item 3 Item 4

21. Kanban Todo In Progress Done Item 1 Item 2 Item 3 Item 4

22. Kanban Todo In Progress Done Item 5 Item 1 Item 2 Item 3 Item 6 Monitor WIP Item 4

23. Kanban

24. Information Radiators Visualize the Workflow Self Organizing Teams Empower the workers Accountability Stop the line culture

25. Build Integrity In Perceived Integrity Users ‘love’ the product Emotional reaction Conceptual Integrity

26. Lean vs. Scrum Why Lean is the resonating What and How Scrum is a detailed recipe