Muda, Mura, and Muri: Some Tips for Fine-Tuning the Flow
Definition
The three concepts are interrelated: Muri (overburden) generates Mura (variability), which in turn produces Muda (waste). Addressing only Muda without tackling the root causes (Muri and Mura) yields temporary improvements that do not last.
Muda
Muda is any activity that consumes resources without generating value for the customer. The Toyota system identifies seven types of Muda that apply to both manufacturing and knowledge work:
- Overproduction: producing more than the customer needs or before they need it. In software: developing features that no one will use.
- Waiting: time during which work sits idle, waiting for the next step. In software: stories waiting for review, approval, or integration.
- Transportation: moving materials or information unnecessarily. In software: handoffs of information between departments or teams.
- Overprocessing: applying more process than necessary. In software: excessive documentation, redundant meetings.
- Inventory: accumulating more work than can be processed. In software: a backlog with hundreds of unrefined stories.
- Motion: unnecessary movement of people or data. In software: frequent context switching between projects.
- Defects: work that does not meet requirements and must be redone. In software: bugs, technical debt.
Determining Factors of Mura and Muri
Mura (unevenness or variability) is the fluctuation in workflow: peaks in workload followed by periods of inactivity. In agile teams, Mura appears when:
- Stories arrive in the sprint with highly uneven sizes.
- External demand (incidents, urgent requests) interrupts the planned flow.
- The team's velocity varies widely between sprints for no clear reason.
Mura is a source of Muda: workload peaks generate overprocessing and defects; troughs generate waiting and inventory.
Muri
Muri (overload) is demanding more from people or processes than they can sustainably deliver. In agile teams, Muri appears when:
- Sprints are planned with more work than the team can complete.
- The team systematically works overtime to meet commitments.
- People are assigned to too many projects in parallel.
Muri generates Mura (the team works unevenly to compensate for the overload) and Muda (rushed work produces defects that have to be reworked).
Common mistake
Tackling Muda without resolving Mura and Muri. Identifying and eliminating waste (Muda) produces visible short-term improvements, but if the root cause is overburden (Muri) or variability (Mura), the waste reappears. Sustained improvement requires leveling the workload and eliminating the sources of variability before optimizing individual activities.
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.