Lean Software Development is a method that applies Lean principles to software creation, focusing on eliminating waste, accelerating delivery, and improving quality. It provides decision heuristics and process adaptations to optimize flow, value, and learning across teams and product lines. Useful for continuous improvement and organisational streamlining.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Executable approach: can be applied and produces an outcome.
What organizes, connects, or makes decisions possible.
Lean Software Development applies Lean principles to software development. Teams maximize customer value by reducing waste, building quality in, learning quickly, and keeping work flowing evenly.
Mary and Tom Poppendieck systematized the approach in their 2003 book “Lean Software Development: An Agile Toolkit”. They translated seven Lean principles from industrial production into agile software work and connected them with practical techniques.
Follow an idea from start to usable feedback: unfinished work waits, is refined, built, checked, and released. Every handoff, delay, or feature without value increases inventory; small batches, built-in quality, and deferred commitment keep flow able to learn.
Effort that adds neither customer value nor learning is made visible and questioned.
Tests, reviews, and engineering practices prevent defects from being discovered only at the end.
Small deliveries shorten feedback paths and enable decisions based on new evidence.
Lean Software Development helps with prioritization, process improvement, and fast feedback design. Its principles require contextual judgment: a blanket pursuit of waste can devalue necessary documentation, security work, or exploration.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.