Value Stream Analysis and Mapping for Project Management

From apppm
(Difference between revisions)
Jump to: navigation, search
(History)
(History)
Line 22: Line 22:
 
*Pull: acting only to satisfy customer needs, rather than forcing, or pushing, a product upon the marketplace.
 
*Pull: acting only to satisfy customer needs, rather than forcing, or pushing, a product upon the marketplace.
 
*Perfection: continuously and relentlessly improving the value, value stream, flow, and pull in business operations.
 
*Perfection: continuously and relentlessly improving the value, value stream, flow, and pull in business operations.
 
 
 
 
 
 
The use of VSA/M began as a tool for manufacturing processes improvement.
 
  
 
==Methodology==
 
==Methodology==

Revision as of 10:21, 22 September 2016


Value Stream Analysis and Mapping (VSA/M) is a tool for business process improvement.[1] Value Stream Analysis (VSA) is a method that implements lean principles for the examination of business processes. The tool, focus on the development of tasks which add value to the final product, efficiently linked together to form a continuously flowing stream of value.[1]

Contents

History

In order to understand its origins we must look back into the early 40s. By then, Toyota was trying to compete with the American automobile market by productivity means. Taiichi Ohno in 1956 traveled to the US in order to visit the automobile plants and see how could he improve its production system back in Japan. Despite what he saw on those production plants, what catches his attention is the self-service supermarkets in which he could choose exactly what he wanted and how much of it. That idea was efficient as well as timely saver for him and where to become later the fundamentals for pursuing manufacturing improvements. Along the next years Ohno will develop this production system on a systematic framework based on Lean and Just-In-Time principles. Toyota defined six elementary rules[2]:

  • Never send defective products downstream to the next process
  • Each process only orders what it currently needs from the upstream process
  • Each process only produces the quantity ordered by the downstream process
  • Maintain a level rate of production
  • Use Kanban to fine-tune the rate of production
  • Work to reach a stable rate of production

These first studies where focused mainly on manufacturing processes in spite of process design. But the principles can still be applied either to shop floor and non-shop floor activities.

As Womack and Jones describe it, the main principles of lean are[3][4]

  • Value: providing the customer with the right product, for the right price, at the right time.
  • Value Stream: the set of actions that bring a product from concept to realization, order to delivery, or raw material to finished good
  • Flow: seamless movement through value-creating steps.
  • Pull: acting only to satisfy customer needs, rather than forcing, or pushing, a product upon the marketplace.
  • Perfection: continuously and relentlessly improving the value, value stream, flow, and pull in business operations.

Methodology

Application

Discussion

Value Stream Mapping can be thought as a tool which facilitates the transformation from a traditional manufacturing company to a Lean Enterprise. It is a planning tool to target ideal processes and roadmaps to desired improvements.[5]

Advantages

Limitations

Related Articles

The lessons from Toyota for product development had been captured by Fujimoto and Clark[6] and Ward and Sobek.[7][1] Follow the references for further study.

Key references

  1. 1.0 1.1 1.2 http://dspace.mit.edu/bitstream/handle/1721.1/7333/Value%20Stream%20Analysis%20and%20Mapping.pdf?sequence=1
  2. http://world-class-manufacturing.com/Kanban/kanban.html
  3. http://www.lean.org/Bookstore/ProductDetails.cfm?SelectedProductId=160
  4. http://web.mit.edu/esd.83/www/notebook/WomackJones.PDF
  5. http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.201.6852&rep=rep1&type=pdf
  6. https://books.google.fr/books?id=7cCAASTW6IQC&hl=es
  7. https://books.google.dk/books/about/Principles_that_Shape_Product_Developmen.html?id=ZbYGtwAACAAJ&redir_esc=y
Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox