Posts categorized as: seven-wastes-series

Want to Ship Code Faster? Find Defects Faster

Published by Matt Stine

Defects are the last of the Seven Wastes of Software Development. The Seven Wastes were identified by Mary and Tom Poppendieck, the foreparents of Lean Software Development. It grew out of their efforts to understand and apply the principles of Lean Manufacturing to software engineering. Waste elimination is the essence of Lean’s archetype, the Toyota Production System: All we are doing is looking at the timeline from the moment a customer gives us an order to the point when we collect the cash.

Want to Ship Code Faster? Stop Task Switching

Published by Matt Stine

Task Switching is the sixth of the Seven Wastes of Software Development. The Seven Wastes were identified by Mary and Tom Poppendieck, the foreparents of Lean Software Development. It grew out of their efforts to understand and apply the principles of Lean Manufacturing to software engineering. Waste elimination is the essence of Lean’s archetype, the Toyota Production System: All we are doing is looking at the timeline from the moment a customer gives us an order to the point when we collect the cash.

Want to Ship Code Faster? Don't Delay Eliminating Delays

Published by Matt Stine

Delays are the fifth of the Seven Wastes of Software Development. The Seven Wastes were identified by Mary and Tom Poppendieck, the foreparents of Lean Software Development. It grew out of their efforts to understand and apply the principles of Lean Manufacturing to software engineering. Waste elimination is the essence of Lean’s archetype, the Toyota Production System: All we are doing is looking at the timeline from the moment a customer gives us an order to the point when we collect the cash.

Want to Ship Code Faster? Stop Playing the Telephone Game

Published by Matt Stine

Handoffs are the fourth of the Seven Wastes of Software Development. The Seven Wastes were identified by Mary and Tom Poppendieck, the foreparents of Lean Software Development. It grew out of their efforts to understand and apply the principles of Lean Manufacturing to software engineering. Waste elimination is the essence of Lean’s archetype, the Toyota Production System: All we are doing is looking at the timeline from the moment a customer gives us an order to the point when we collect the cash.

Want to Ship Code Faster? Stop Learning Things Twice

Published by Matt Stine

Relearning is the third of the Seven Wastes of Software Development. The Seven Wastes were identified by Mary and Tom Poppendieck, the foreparents of Lean Software Development. It grew out of their efforts to understand and apply the principles of Lean Manufacturing to software engineering. Waste elimination is the essence of Lean’s archetype, the Toyota Production System: All we are doing is looking at the timeline from the moment a customer gives us an order to the point when we collect the cash.

Want to Ship Code Faster? Stop Building Extra Features

Published by Matt Stine

Extra Features are the second of the Seven Wastes of Software Development. The Seven Wastes were identified by Mary and Tom Poppendieck, the foreparents of Lean Software Development. It grew out of their efforts to understand and apply the principles of Lean Manufacturing to software engineering. Waste elimination is the essence of Lean’s archetype, the Toyota Production System: All we are doing is looking at the timeline from the moment a customer gives us an order to the point when we collect the cash.

Want to Ship Code Faster? Minimize Partially Done Work

Published by Matt Stine

Partially Done Work is the first of the Seven Wastes of Software Development. The Seven Wastes were identified by Mary and Tom Poppendieck, the foreparents of Lean Software Development. It grew out of their efforts to understand and apply the principles of Lean Manufacturing to software engineering. Waste elimination is the essence of Lean’s archetype, the Toyota Production System: All we are doing is looking at the timeline from the moment a customer gives us an order to the point when we collect the cash.

Eliminating These 7 Wastes Will Level Up the Value Your Software Delivers

Published by Matt Stine

Waste elimination is critical to delivering value through software. In the late 1940s, Toyota had a problem. Manufacturing was expensive, so prices were high. But the typical car buyer in Japan was light on cash. Reducing the cost of manufacturing was the only way to sell cars. Mass production could have solved the problem, but Japan’s economy wasn’t large enough to create demand for thousands of cars. Toyota had to find another way, and they turned to Taiichi Ohno.