Value stream mapping

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
File:ValueStreamMapParts.png
Value stream mapping usually employs standard symbols to represent items and processes, therefore knowledge of these symbols is essential to correctly interpret the production system problems.

Value stream mapping is a lean-management method for analyzing the current state and designing a future state for the series of events that take a product or service from its beginning through to the customer. At Toyota, it is known as "material and information flow mapping".[1] It can be applied to nearly any value chain.

Using the Method

  1. Planning and preparation. Identify the target product family or service. Create a flow, define the problem, set the goals and objectives, and select the mapping team. Discuss the flow with the management team.[2]
  2. Draw while on the shop floor a current state value stream map, which shows the current steps, delays, and information flows required to deliver the target product or service. This may be a production flow (raw materials to consumer) or a design flow (concept to launch). There are 'standard'[citation needed] symbols for representing supply chain entities.
  3. Assess the current state value stream map in terms of creating flow by eliminating waste.
  4. Draw a future state value stream map.
  5. Work toward the future state condition.[3]

Applications

File:VSM1.JPG
Value Stream Maps are usually drawn using a set of standard symbols, some of which can be seen here.

Value stream mapping has supporting methods that are often used in Lean environments to analyze and design flows at the system level (across multiple processes).

Although value stream mapping is often associated with manufacturing, it is also used in logistics, supply chain, service related industries, healthcare,[4][5] software development,[6][7] product development,[8] and administrative and office processes.[9]

In a build-to-the-standard form, Shigeo Shingo[10] suggests that the value-adding steps be drawn across the centre of the map and the non-value-adding steps be represented in vertical lines at right angles to the value stream. Thus, the activities become easily separated into the value stream, which is the focus of one type of attention, and the 'waste' steps, another type. He calls the value stream the process and the non-value streams the operations. The thinking here is that the non-value-adding steps are often preparatory or tidying up to the value-adding step and are closely associated with the person or machine/workstation that executes that value-adding step. Therefore, each vertical line is the 'story' of a person or workstation whilst the horizontal line represents the 'story' of the product being created.

Value stream mapping is a recognised method used as part of Six Sigma methodologies.[11]

Value stream mapping in Software Engineering

The success of Lean in manufacturing and production has led to an interest in its adoption in software development. However, it was noted that the current literature on adoption of Lean in software development had a disconnect between the high-level principles and the concrete practices related to lean and agile software development. The literature had also a limited focus on wastes that were literally mapped from the categories identified for manufacturing.[12] This was ignoring the transformation that lean thinking has itself undergone and moved away from the focus on "removal of waste" to "creating and delivering value" [13] The use of value stream mapping as suggested by the pioneer authors of the field Womack and Jones [14] was identified as the missing link in the current literature on lean in software development.

Value stream mapping analyses both material (artifact) and information flow.[15] The following two resources exemplify the use of VSM to do it in the context of software process improvement in industrial settings:

  • "Artifact analysis:" analysis of software artifacts like requirements, use case, change request or defect report through the development process [16]
  • "Information flow analysis:" analysis of information flows in the development process [17]

Metrics

A key metrics associated with value stream mapping are value adding times and non value adding times.[18] Non value adding time is called lead time.

Associated analysis methods

Hines and Rich (1997) defined seven value stream mapping tools[19] they are:

  1. Process Activity Mapping
  2. Supply chain responsiveness matrix
  3. Product Variety Funnel
  4. Quality filter mapping
  5. Forrester effect mapping
  6. Decision point analysis
  7. Overall Structure Maps

See also

References

  1. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  2. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  3. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  4. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  5. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  6. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  7. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  8. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  9. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  10. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  11. ↑ "Value Stream Mapping" Article Source: http://www.isixsigma.com/index.php?option=com_k2&view=itemlist&layout=category&task=category&id=90&Itemid=222#
  12. ↑ Ali N.B., Operationalization of lean thinking through value stream mapping with simulation and FLOW [dissertation]. Karlskrona: Department of Software Engineering, Blekinge Institute of Technology; 2015.
  13. ↑ Hines P, Holweg M, Rich N. Learning to evolve: A review of contemporary lean thinking. International Journal of Operations & Production Management. 2004;24(10):994-1011.
  14. ↑ Womack JP, Jones DT. Lean thinking: banish waste and create wealth in your corporation. Rev. and updat [] ed. London: Free Press Business; 2003.
  15. ↑ Rother, Mike, and John Shook. Learning to see: value stream mapping to add value and eliminate muda. Lean Enterprise Institute, 2003.
  16. ↑ Ali NB, Petersen K, Breno Bernard Nicolau de França. Evaluation of simulation-assisted value stream mapping for software product development: Two industrial cases. Information and Software Technology. 2015;68:45.
  17. ↑ Ali NB, Petersen K, Schneider K. FLOW-assisted value stream mapping in the early phases of large-scale software development. Journal of Systems and Software. 2016;111:213-27.
  18. ↑ JANUŠKA, M., PÁLKA, P., ŠŮLOVÁ, D., CHODŮR, M. Value chain of virtual enterprise - Possible modern management concepts and value drivers identification. In Annals of DAAAM for 2009 and 20th International DAAAM Symposium "Intelligent Manufacturing and Automation: Focus on Theory, Practice and Education". Vienna: Danube Adria Association for Automation and Manufacturing, DAAAM, 2009. s. 469-470. ISBN 978-3-901509-70-4 , ISSN: 1726-9679
  19. ↑ Lua error in package.lua at line 80: module 'strict' not found.

External links

Retrieved from "https://infogalactic.com/w/index.php?title=Value_stream_mapping&oldid=3830959"