The Seven Wastes of Software Development (Muda)
Think of "Muda" as anything consuming resources without adding customer value. This Lean concept helps agile teams spot inefficiencies like partially done work and context switching.
The mental model
Muda is a Japanese term for waste, representing any activity in your development process that consumes resources but creates no value for the customer. It's not about working harder; it's about eliminating activities that don't contribute to the final product, like a car factory eliminating unnecessary steps on an assembly line. The goal is to maximize value-adding work by systematically identifying and removing these wasteful activities.
How it works
The concept is applied by categorizing process inefficiencies into seven specific types, adapted from manufacturing for software development. These are: Partially Done Work (work started but not delivered), Extra Features (gold-plating or building things nobody asked for), Relearning (knowledge lost due to poor documentation or team churn), Handoffs (transferring work between people or teams, which introduces delays and miscommunication), Delays (waiting for reviews, approvals, or dependencies), Task Switching (the cognitive overhead of juggling multiple unrelated tasks), and Defects (bugs or quality issues that require rework).
When to use it
Use the Seven Wastes as a lens during retrospectives or process improvement initiatives. It provides a structured framework for teams to ask, "What is slowing us down?" It's especially powerful for mature agile teams looking to move beyond basic scrum ceremonies and achieve a state of continuous flow. It helps quantify and categorize problems that feel vague, like "things feel slow."
When not to use it
Avoid using "waste" as a term to blame individuals or teams; the focus must be on the process, not the people. It is also not a one-time checklist. Blindly eliminating something that looks like waste without understanding its purpose can be harmful. For example, some "delays" might be necessary for critical security reviews, and some "extra features" might be strategic bets. The context of the system and business goals is paramount.
One canonical example
A classic example is "Partially Done Work." Imagine a developer finishes coding a feature, but it sits for three weeks waiting for a QA environment to become available. During that time, the code is inventory. It has no value to the customer, it risks becoming outdated as other code changes, and the developer loses context, making any future bug fixes on it more difficult. This "waste" of waiting ties up capital (developer salary) in an asset that isn't delivering returns.
Interview question
What is the primary objective when an agile team applies the concept of Muda to its development process?
- a.To strictly minimize all forms of delays and handoffs within the workflow.
- b.To ensure every feature developed is a "gold-plated" solution meeting all possible future needs.
- c.To assign blame to individuals or teams responsible for inefficiencies.
- d.To identify and eliminate activities that consume resources without adding value for the customer.Correct
Why? this is the answer
The core purpose of Muda is to identify and remove activities that consume resources but create no customer value, thereby maximizing value-adding work. While delays and handoffs are wastes, the card explicitly warns against blindly eliminating all forms, as some might be necessary, making option A incorrect.
Just read this? Test yourself on what you have been reading.
Read the original → en.wikipedia.org
Put your scrolling time to good use
Learn one idea, try a quiz and save useful cards for revision. Tezvyn makes it easy to learn and stay current in your tech field, a few minutes at a time.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Every open role lists the topics its interview covers, so you can prepare for the real thing rather than guessing.
See open roles