DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Zones

Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks

The software you build is only as secure as the code that powers it. Learn how malicious code creeps into your software supply chain.

Apache Cassandra combines the benefits of major NoSQL databases to support data management needs not covered by traditional RDBMS vendors.

Generative AI has transformed nearly every industry. How can you leverage GenAI to improve your productivity and efficiency?

Modernize your data layer. Learn how to design cloud-native database architectures to meet the evolving demands of AI and GenAI workloads.

Related

  • Is Agile Right for Every Project? When To Use It and When To Avoid It
  • Breaking Bottlenecks: Applying the Theory of Constraints to Software Development
  • 7 Effective Conflict Resolution Strategies for Software Development Teams
  • Seamless Security Integration Strategies in Software Development

Trending

  • Beyond ChatGPT, AI Reasoning 2.0: Engineering AI Models With Human-Like Reasoning
  • Testing SingleStore's MCP Server
  • What Is Plagiarism? How to Avoid It and Cite Sources
  • Debugging With Confidence in the Age of Observability-First Systems

The Seven Wastes of Software Development

If you are not creating value in your product, consider whether your there are steps in your process that can be cut out to reduce waste.

By 
Matt Stine user avatar
Matt Stine
·
Aug. 11, 10 · Analysis
Likes (4)
Comment
Save
Tweet
Share
137.9K Views

Join the DZone community and get the full member experience.

Join For Free

Today I'd like to start a brand new series, the focus of which is the elimination of waste from our software development efforts. Waste elimination can be traced all the way back to the the mid-1900's, the birth of lean manufacturing, and the Toyota Production System (TPS).

Taiichi Ohno, father of the TPS, called it a management system for "the absolute elimination of waste" [1].

But what exactly is waste, and why is its elimination important?

Read the other parts in this series:

 

To understand Ohno's focus on waste elimination, you must first understand a bit of the problem faced by Toyota in the late 1940's. Manufacturing an automobile was an expensive process, and thus cars carried hefty price tags. And yet, the typical potential car buyer in Japan didn't have a great deal of money. For Toyota to succeed, they had to reduce the price of cars by reducing the cost of manufacturing.

At that time, the only recognized means of manufacturing cost reduction was mass production. This would mean producing thousands of units of the same type of car. However, Japan's economy simply wasn't large enough to create the necessary demand for thousands of cars. Toyota had to find another way.

Ohno's TPS was that other way. This is how Ohno described the essence of the TPS:

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. And we are reducing that timeline by removing the non-value-added wastes [1].


And there you have it. Look at the manufacturing process, strip out anything that does not add value to the customer, and you'll arrive at a cheaper, faster way of building a car. Then continually improve by iterating on the waste elimination process.

At the heart of lean software development is the same principle: eliminate waste. In order to eliminate waste, you must first be able to recognize it.

A wise man once said, "My goal is to make you so familiar with the truth that when a counterfeit looms on the horizon you'll know it instantly." The best way to recognize waste is to become intimately familiar with its opposite: value. I took a long look at value in my earlier article,  User stories are one effective means for understanding what your customers truly value.

Once you have a handle on value, it's time to start looking for waste. To begin, map out all of the activities that must occur in your organization from the time a required software feature is identified until the time the customer begins deriving value from that feature. Next, uncover your biggest sources of waste and eliminate them. Rinse and repeat!

To help us in our search for waste, it helps to visit the work of another of TPS's forefathers, Shigeo Shingo. Shingo identified seven major types of manufacturing waste [2]:

  1. Inventory
  2. Overproduction
  3. Extra Processing
  4. Transportation
  5. Waiting
  6. Motion
  7. Defects

Mary and Tom Poppendieck later translated these seven wastes into "The Seven Wastes of Software Development" [3]:

  1. Partially Done Work
  2. Extra Features
  3. Relearning
  4. Handoffs
  5. Delays
  6. Task Switching
  7. Defects

Over the next seven weeks we'll look at examine each of these sources of wastes in detail. We'll look at some of their common manifestations, both in our coding practices and in our development methodologies. We'll also examine strategies for eliminating each of these wastes from our development efforts. Until next time!


References

[1] Ohno, Taiichi. Toyota Production System: Beyond Large Scale Production. Productivity Press, 1988.

[2] Shingo, Shigeo. A Study of the Toyota Production System. Productivity Press, 1981.

[3] Poppendieck, Mary and Tom. Implementing Lean Software Development: From Concept to Cash. Addison-Wesley, 2006.

Software development

Opinions expressed by DZone contributors are their own.

Related

  • Is Agile Right for Every Project? When To Use It and When To Avoid It
  • Breaking Bottlenecks: Applying the Theory of Constraints to Software Development
  • 7 Effective Conflict Resolution Strategies for Software Development Teams
  • Seamless Security Integration Strategies in Software Development

Partner Resources

×

Comments

The likes didn't load as expected. Please refresh the page and try again.

ABOUT US

  • About DZone
  • Support and feedback
  • Community research
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 100
  • Nashville, TN 37211
  • support@dzone.com

Let's be friends: