Lean Software Development: Difference between revisions
Jump to navigation
Jump to search
(Created page with "Category:Agile:ArticlesCategory:Agile:Lean Software DevelopmentCategory:Agile Lean Software Development was introduced by Mary and Tom Poppendeick with their book...") |
(No difference)
|
Revision as of 04:35, 10 January 2019
Lean Software Development was introduced by Mary and Tom Poppendeick with their book Lean Software Development, an Agile Toolkit in 2003, and was subsequently followed up with 2 additional books on the subject.
The approach is heavily influenced with Lean ideas to provide a suite of principles and tools for software development.
Principles
- Optimise The Whole
- Focus on Customers
- Energise Workers
- Reduce Friction
- Enhance Learning
- Increase Flow
- Build Quality In
- Keep Getting Better
Tools
- Seeing Waste
- Value Stream Mapping
- Feedback
- Iterations
- Synchronisation
- Set Based Development
- Options Thinking
- The Last Responsible Moment
- Making Decisions
- Pull Systems
- Queuing Theory
- Cost of Delay
- Self Determination
- Motivation
- Leadership
- Expertise
- Perceived Integrity
- Conceptual Integrity
- Refactoring
- Testing
- Measuring
- Contracts
Value
Waste
Speed
People
Knowledge
Quality
Partners
Journey
Systems Thinking
Technical Excellence
Relentless Improvement
Aligned Leaders
See Also
References
- Lean Software Development, an Agile Toolkit, Poppendieck M, Poppendieck T, 2003
- Implementing Lean Software Development, From Concept To Cash, Poppendieck M, Poppendieck T, 2006
- Leading Lean SoftwareDevelopment, Results Are Not The Point, Poppendieck M, Poppendieck T, 2009
- http://www.poppendieck.com/, accessed January 2019