Seven wastes of software development

Similar to what TPS identified as seven categories of waste in manufacturing, also software development has its own wastes.
Read more
Article

Similar to what Toyota Production System identified as seven categories of waste in manufacturing, also software development has its own wastes.

Partially done work

The work which is not complete does not bring any value. Furthermore, it creates additional constraints to keep it in a usable state.

7 wastes of software development - Partially done work

Extra features

Understanding customer needs is crucial to delivering real value by building the right thing.

7 wastes of software development - Extra features

Relearning

Developing software is heavily based on learning. Making the same mistakes over again can be omitted by capitalizing on the first occurrence of a mistake.

7 wastes of software development - Relearning

Handoffs

Handoffs create extra work by a need to shift information. A lot of information is lost during these shifts.

7 wastes of software development - Handoffs

Delays

In order to keep the context fresh fast feedback is important. The bigger the delay in getting feedback the harder it becomes to capitalize on it.

7 wastes of software development - Delays

Task switching

Every context switch creates a must to change focus, and readjust for other tasks, resulting in lower productivity.

7 wastes of software development - Task switching

Defects

Creating defects boomerang back, creating extra work, and slowing down new development

7 wastes of software development - Defects

Similar posters

Eisenhower Matrix
Eisenhower Matrix The Eisenhower Matrix, also known as the Urgent-Important Matrix, is a tool for organizing tasks by their urgency and importance to improve productivity and decision-making. It divides tasks into four quadrants based on these criteria. Do Important and Urgent Tasks in this quadrant require immediate attention and are essential to your goals. These are often...
Maker's vs Manager's schedule
Maker's vs Manager's schedule The differences between a maker’s and a manager’s schedules stem from their respective workflows’ distinct nature. Makers rely on uninterrupted time blocks to tackle complex, creative problems requiring deep focus and sustained attention. Managers need flexibility to oversee multiple responsibilities, make decisions, and collaborate effectively across teams. As such, it is essential to thoughtfully assess...
Mission Statement
Mission Statement Long-term organization purpose, values and objectives. It should describe why it matters. This way it contributes to identity creation.
Value Stream Mapping
Value Stream Mapping The Value Stream Mapping is a Lean technique for managing flow and improving processes allowing to track the flow through a process.
Minto Pyramid
Minto Pyramid The Minto Pyramid Principle, a communication framework, advocates for a top-down approach to convey messages effectively
Spotify Health Check
Spotify Health Check The Spotify Health Check is a workshop, where teams assess their project and collaboration using 11 dimensions.
Maslow's Hierarchy Of Needs
Maslow's Hierarchy Of Needs Maslow's hierarchy of needs links basic human needs and desires, emphasizing that survival needs must be met before higher needs.
RACI Matrix
RACI Matrix RACI Matrix/Chart is the type of responsibility assignment matrix for effective work organization, communicating the responsibilities.
CEDAR Feedback
CEDAR Feedback CEDAR is a structured feedback model providing coaching opportunities via repeated revisiting and readjusting of the feedback and the goals.
STATIK Kanban
STATIK Kanban The Systems Thinking Approach To Introducing Kanban (STATIK) is a repeatable way to start with Kanban resulting in continuous improvement.