Agile Engineering Kanban Lean

Seven wastes of software development

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

Get PDF

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.

Extra features

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

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.

Handoffs

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

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.

Task switching

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

Defects

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

Resources

hackernoon.com agility.im hackernoon.com

Similar posters

RACI Matrix RACI Matrix/Chart is the type of responsibility assignment matrix for effective work organization, communicating the responsibilities.

CEDAR Feedback CEDAR is a structured feedback model providing coaching opportunities via repeated revisiting and readjusting of the feedback and the goals.

STATIK Kanban The Systems Thinking Approach To Introducing Kanban (STATIK) is a repeatable way to start with Kanban resulting in continuous improvement.

Data Model Canvas The Data Product Canvas is a framework for developing data products based organized into 10 blocks within 3 domain areas.

Kanban Practices Visualize Visualizing your work provides transparency, identifying the bottlenecks. Create cards for the items you work on. Think of the workflow – statuses that work items go through to make implicit policies explicit, which enable learning how the work works. Limit Work In Process Stop starting, start finishing. Limit the number of items being worked...

Theory Of Constraints The Theory of constraints says the throughput of any system is limited by at least one constraint slowing it down.

Classes of Service (CoS) Classes of service (CoS) provide a transparent way of categorizing the incoming work items and ensuring they are properly prioritized and governed to lead to meeting customer expectations. They enable managing risk, priorities, and cost of delay. Expedite High-priority items that should be worked on as soon as possible. Expedite class work items have critical...

Core Kanban Practices One of the few rules or practices which are the foundation of Kanban are its 3 core practices: Visualize, Limit WIP, and Manage flow.

The prime directive of agile software development Acronymat poster: The prime directive of agile software development - Never be blocked, the system must work all the time.

AIDAOR The AIDAOR is a hierarchical model, where a persona moves through a series of cognitive steps before and after making a purchase decision.