Want to create interactive content? It’s easy in Genially!

Get started free

Lean Software Development

JESHUA ABRAHAM PEREZ DIAZ

Created on September 17, 2025

Start designing with a free template

Discover more than 1500 professional designs like these:

Transcript

Methodology from Lean Manufacturing (Toyota), applied to software.

Focus: eliminate waste, deliver value.

Derived from Toyota Production System.

What it is:

Use cases:

- Startups, MVPs - Fast feedback cycles - Cost reduction environments

Origin / History:

Lean Software Development

Jeshua Abraham Perez Diaz TDSM3A

Mary & Tom Poppendieck, 2003.

Disadvantages:

Principles / Stages:

1. Eliminate Waste 2. Amplify Learning 3. Defer Commitment

- Hard cultural change - Defining 'waste' is tricky - Risk of under-specifying - Needs discipline

Advantages:

- Faster delivery - Less waste - Higher quality

4. Deliver Fast 5. Build Quality 6. Respect People 7. Optimize the Whole

- Customer focus - Empowered teams

Advantages / Benefits

- Faster delivery / reduced time‐to‐market. - Reduced waste (cost, effort). - Higher quality (build quality in). - Greater customer satisfaction & better focus on customer value. - Empowered teams; respect people.

What is Lean Software Development

A methodology that applies principles from lean manufacturing (Toyota Production System) to software development. Focuses on eliminating waste, maximizing value, speeding delivery, etc.

Disadvantages / Challenges / Limitations

- Cultural change / resistance (lean requires mindset shifts). - Hard to identify what is truly “waste” in software dev. - Overemphasis on minimalism can lead to missing features or under‐specification. - Difficulties in measuring some aspects of value or waste. - Needs mature team / discipline.

Origins / History

- Originated from lean manufacturing / TPS (Toyota). - First applied explicitly to software in “Lean Software Development: An Agile Toolkit” by Mary Poppendieck & Tom Poppendieck in 2003.

Truquito:

La interactividad es la pieza clave para captar el interés y la atención de tu audiencia. Un genially es interactivo porque tu público explora y se relaciona con él.

When / In what cases is it used

- Projects where speed to market and efficiency are critical. - Environments with frequent feedback & changes. - Startups with MVP focus. - When teams want to optimize costs and reduce overhead. - Also can be combined with Agile, or used within Kanban systems.

Key Principles / Stages

The lean principles often given are (seven): 1. Eliminate Waste 2. Amplify Learning 3. Defer Commitment (Decide as Late as Possible) 4. Deliver Fast 5. Build Quality In 6. Respect People 7. Optimize the Whole