Ir al contenido

Lean Software Development

De Scrum Manager BoK
Esta página es una versión traducida de la página Lean Software Development. La traducción está completa al 100 %.
⏱ 4 min  ·  📅 2026
Lean Software Development (LSD) is the application of the principles of lean manufacturing to software development. It was formulated by Mary and Tom Poppendieck in their book Lean Software Development: An Agile Toolkit (2003) and is one of the foundational frameworks of the agile movement, although less well known than Scrum or XP.

The Seven Principles

Mary and Tom Poppendieck identified seven principles that translate lean thinking into the context of software development:

1. Eliminate Waste

In lean manufacturing, waste is anything that does not add value for the customer. In software, the Poppendiecks identified seven equivalent types of waste: partially done work, extra features, relearning, handoffs, delays, task switching, and defects. Eliminating waste is the first principle because everything else flows from it.

2. Amplify learning

Software development is a process of discovery: requirements become clearer as the system is built. Instead of trying to specify everything up front, Lean Software Development proposes amplifying learning through short feedback cycles, frequent testing, and reviews with the customer.

3. Decide as late as possible

Making irreversible decisions too early, before having enough information, is a source of waste. LSD proposes postponing decisions until the moment when the most information is available, without delaying them to the point where they become urgent.

4. Deliver as fast as possible

Rapid delivery of value to the customer reduces risk, generates early feedback, and enables adaptation. Short delivery cycles are the best way to learn what the customer really needs.

5. Empower the team

The people closest to the work are the ones who know it best. LSD proposes that technical decisions be made by developers, not managers, and that the role of leadership be to create the conditions for the team to do its work with autonomy and quality.

6. Build Integrity In

Quality cannot be added at the end as a layer: it has to be built into the process from the start. This includes both perceived integrity (the user's experience of the system) and conceptual integrity (the system forming a coherent whole).

7. See the Whole

Complex systems cannot be optimized by optimizing each part separately. Seeing the whole means understanding interdependencies, avoiding local suboptimization, and making sure that local improvements contribute to the value of the system as a whole.

Lean Software Development and AI

The seven LSD principles are especially relevant in the context of AI-assisted development:

  • Eliminate waste: code generated without review that later has to be rewritten is waste. A strengthened DoD and human review of AI-generated code are lean mechanisms for eliminating defects.
  • Amplify learning: rapid prototypes built with AI are a powerful learning tool, provided they are treated as learning artifacts and not as production code.
  • See the whole: local optimization with AI (generating code very quickly in one part of the system) can create systemic problems if the coherence of the whole is not taken into account.

References

Poppendieck, Mary; Poppendieck, Tom

  • (2003). Lean Software Development: An Agile Toolkit. Addison-Wesley.
  • (2006). Implementing Lean Software Development: From Concept to Cash. Addison-Wesley.

See also

Want to advance in agility? You can search for course and exam calls or go at your own pace by becoming a member of the Agile Club. This membership includes exclusive resources, e-learning classrooms, and access to Skill Arena: a space to practice and measure your agile skills at your own pace.