Lean Principles and Software Architecture: The Waste of Information Transformation

Agile , Architecture , Lean Add comments

By Nanette Brown, Senior Member of the Technical Staff
Research, Technology, and System Solutions program

Nanette BrownOccasionally this blog will highlight different posts from the SEI blogosphere. Today’s post is from the SATURN Network blog by Nanette Brown, a senior member of the technical staff in the SEI’s Research, Technology, and System Solutions program. This post, the third in a series on lean principles and architecture, continues the discussion on the eight types of waste identified in Lean manufacturing and how these types of waste manifst themselves in software development. The focus of this post is on mapping the waste of motion and the waste of transportation from manufacturing to the waste of information transformation in software development.

To

Share this

Share on Facebook Send to your Twitter page  Save to del.ico.us  Save to LinkedIn  Digg this  Stumble this page.  Save this page on your Google Home Page 

2 responses to “Lean Principles and Software Architecture: The Waste of Information Transformation”

  1. David Bueford Says:
    Hello I'm a lean practitioner familiar with the 7 wastes

    1. Overproduction.
    2. Waiting
    3. Transporting
    4. Inappropriate Processing
    5. Excess Inventory
    6. Excess Motion
    7. Defects

    What is the eighth?
    Also you have a very informative blog keep up the good work!
  2. Nanette Brown Says:
    Hi David -

    Thanks for your comment.

    You are correct that in the original Toyota Production System, Taiichi Ohno identified 7 types of waste. At a later point in time an 8th type of waste was added, the waste of unused employee creativity.


Add Comment

Leave this field empty: