Value Stream Analysis and Mapping for Project Management

From apppm
(Difference between revisions)
Jump to: navigation, search
(→‎Application)
(→‎Application)
Line 229: Line 229:
  
 
The next table describes with examples each one of the seven info-wastes since it is very important to understand them in order to find on the state map.
 
The next table describes with examples each one of the seven info-wastes since it is very important to understand them in order to find on the state map.
 +
 +
 +
{| class="wikitable"
 +
|-
 +
! '''Types of Information Waste'''
 +
! '''Examples'''
 +
! '''Causes'''
 +
|-
 +
| '''Waiting'''
 +
Idle time due to unavailable information
 +
| People waiting for information
 +
|
 +
*Lack of access
 +
*Untimely updating of data bases
 +
*Multiple approvals
 +
*Poorly designed or executed process to provide information
 +
|-
 +
|
 +
| Information waiting for people
 +
|
 +
*Information created too soon may be obsolete by the time it is used
 +
|-
 +
| '''Inventory'''
 +
Information that is unused or is “work in progress”
 +
| Too much information
 +
|
 +
*Poor understanding of user needs
 +
|-
 +
|
 +
| Multiple/redundant sources
 +
|
 +
*Tendency for everybody to maintain their own files
 +
|-
 +
|
 +
| Outdated/obsolete information
 +
|
 +
*Lack of “version control”
 +
*Lack of disciplined system for updating new and purging old information
 +
*Inadequate archiving standards or practices
 +
|-
 +
|
 +
| “Just-in-case” information
 +
|
 +
*Collection, processing and storage of every element of data that process participants can think of, whether or not a specific end use has been identified
 +
|-
 +
| '''Excessive Processing'''
 +
Information processing beyond requirements
 +
| Excessive/custom formatting
 +
|
 +
*Lack of standardization
 +
|-
 +
|
 +
| Numerous, fragmented reports
 +
|
 +
*Poor output design
 +
*Lack of understanding of the needs of the users of process outputs
 +
|-
 +
|
 +
| Unnecessary serial processing
 +
|
 +
*Poor system design
 +
*Lack of understanding of concurrent processing capabilities
 +
|-
 +
|
 +
| Excessive approvals for information release
 +
|
 +
*Stove pipe, command and control mentality
 +
*Turf protection
 +
|-
 +
| '''Over Production'''
 +
Producing, distributing more information than needed
 +
| Unnecessary detail and accuracy
 +
|
 +
*Tendency to “over-design”
 +
*More detail than necessary in early
 +
design
 +
|-
 +
|
 +
| Pushing, not pulling data, information
 +
|
 +
*Uncontrolled process
 +
|-
 +
|
 +
| Over-dissemination
 +
|
 +
*Poor understanding of each
 +
participant’s needs
 +
*“Send all information to everyone,”
 +
rather than to meet specific needs
 +
|-
 +
| '''Transportation'''
 +
Unnecessary movement of information between people, organizations, or systems
 +
| Information handled by multiple people before arriving at user
 +
|
 +
*Lack of direct access due to IT system limits, organizational inefficiencies, knowledge hoarding, security issues
 +
|-
 +
|
 +
| Information hunting
 +
|
 +
*Lack of clear information flow paths, failure of process to produce information needed
 +
|-
 +
|
 +
| Data re-formatting or reentry
 +
|
 +
*Incompatible information types (drawings vs. digital descriptions)
 +
*Incompatible software systems or tools
 +
*Lack of availability, knowledge, or training in conversion and linking systems
 +
|-
 +
|
 +
| Switching computers (e.g., CAD to PC) to access information
 +
|
 +
*Software/hardware incompatibilities
 +
*IS support
 +
|-
 +
| '''UnnecessaryMotion'''
 +
Unnecessary human movement (physical or user movement between tools or system)
 +
| Walking to information, retrieving printed materials
 +
|
 +
*Lack of distributed, direct access
 +
*Lack of on-line access
 +
*Lack of digital versions of heritage information
 +
|-
 +
|
 +
| Excessive keyboard, mouse operations
 +
|
 +
*Lack of training
 +
*Poorly designed user interfaces
 +
*Incompatible software suites
 +
*Too much information to sort through
 +
|-
 +
|
 +
| Poor physical arrangement or organization
 +
|
 +
*Team members not co-located
 +
*Organization structure inhibits formation of right teams
 +
|-
 +
| '''Defects'''
 +
Erroneous data, information, reports
 +
| Errors in data reporting/entries
 +
|
 +
*Human error
 +
*Poorly designed input templates
 +
|-
 +
|
 +
| Errors in information provided to customers
 +
|
 +
*Lack of disciplined reviews, tests, verification
 +
|-
 +
|
 +
| Information does not make sense to user
 +
|
 +
*Raw data delivered when user needs derived information, recommendations, or decisions
 +
|}
  
 
==Discussion==
 
==Discussion==

Revision as of 22:42, 25 September 2016

This article intends to provide a tool for Project Managers who would like to improve their own processes by applying lean concepts. In particular, throughout Value Stream Analysis and Mapping (VSA/M). VSA/M is a tool for business process improvement.[1] The tool, focus on the development of tasks which add value to the final product, efficiently linked together to form a continuous flow stream of value.[1] It is meant to map the processes on a project “as whole “, find its wastes, inefficiencies and non-value-added actions that can be erased in order to achieve a “future state”. Giving insights into the plausible “ideal future state” that it seeks as a long-term goal.

Since this tool has a Lean background, there will be a brief introduction regarding this matter.

Figure 1: PDVSM in a definable process within the PD value stream - Source:[2]

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[3]:

  • 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. And as Womack and Jones describe it, the main principles of lean for product development are[4][5]:

  • 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

The value stream must be analyzed and mapped thoroughly to reduce waste along processes and enable a more efficient flow. Also to move the processes towards a more rapid response for customer pull. For instance, in product development context, this means rapid response towards customer needs. Specially when it comes either to new products or permutations of the existing ones.[1]

On a manufacturing environment

Fundamentally, the method consists on mapping the current state of the process and apply lean techniques. This enables an improved future state of the process. In order to do so, non-value-added tasks are identified. Then, the tasks considered to support the true value-added tasks such as, set-ups, reviews, etc..., are Type I waste. While completely unnecessary tasks such as waiting in the inventory are Type II waste.[5] A number of techniques are then applied once cathegorised these types of waste. Which in the lean manufacturing context include manufacturing cells, Just-In-Time deliveries, aparts supermarkets, etc... Once established the future state map, it is implemented thorough a plan. Which leads to a an improved state that ideally is used to generate further future states. As seen, the process is being continuously improved.

On a Project Management environment

According to the product development team at MIT's Lean Aerospace Initiative[1], the value on a succesful project management is "a capability delivered at the right time, for the right price, as defined by the end user." Now this value stream is effectively emboided on a notional product designed package. Therefore, as the outcome of a value stream it can be evaluated as a stream of value, like in the manufacturing value of stream. This way fitting with other activities around the business cycle to define an overall desired future state as symbolized on Figure 2.

Figure 2: VSM desired state - Source:[6]

In order to extrapolate the VSM under manufacturing principles to a Project Management environment, how does the flow thorough the project management processes translates into? In this case it is information. Information flows thorough the management of the project like on the manufacturing environment material does.[1] The quality of the information flow is characterized by its Form, Fit, Function and Timelines (FFFT). However, value not only comes as a function of the FFFT within the design package, it also comes as the degree the design package allows the end product to match the desires of the customer.

As information flows through the project management process, tasks add value to the information. Since the flows in are made of information instead of physical materials. The next seven info-wastes must enable to identify wastes associated with the information flows[2]:

Types of Information Waste Examples Causes
Waiting

Idle time due to unavailable information

People waiting for information
  • Lack of access
  • Untimely updating of data bases
  • Multiple approvals
  • Poorly designed or executed process to provide information
Information waiting for people
  • Information created too soon may be obsolete by the time it is used
Inventory

Information that is unused or is “work in progress”

Too much information
  • Poor understanding of user needs
Multiple/redundant sources
  • Tendency for everybody to maintain their own files
Outdated/obsolete information
  • Lack of “version control”
  • Lack of disciplined system for updating new and purging old information
  • Inadequate archiving standards or practices
“Just-in-case” information
  • Collection, processing and storage of every element of data that process participants can think of, whether or not a specific end use has been identified
Excessive Processing

Information processing beyond requirements

Excessive/custom formatting
  • Lack of standardization
Numerous, fragmented reports
  • Poor output design
  • Lack of understanding of the needs of the users of process outputs
Unnecessary serial processing
  • Poor system design
  • Lack of understanding of concurrent processing capabilities
Excessive approvals for information release
  • Stove pipe, command and control mentality
  • Turf protection
Over Production

Producing, distributing more information than needed

Unnecessary detail and accuracy
  • Tendency to “over-design”
  • More detail than necessary in early

design

Pushing, not pulling data, information
  • Uncontrolled process
Over-dissemination
  • Poor understanding of each

participant’s needs

  • “Send all information to everyone,”

rather than to meet specific needs

Transportation

Unnecessary movement of information between people, organizations, or systems

Information handled by multiple people before arriving at user
  • Lack of direct access due to IT system limits, organizational inefficiencies, knowledge hoarding, security issues
Information hunting
  • Lack of clear information flow paths, failure of process to produce information needed
Data re-formatting or reentry
  • Incompatible information types (drawings vs. digital descriptions)
  • Incompatible software systems or tools
  • Lack of availability, knowledge, or training in conversion and linking systems
Switching computers (e.g., CAD to PC) to access information
  • Software/hardware incompatibilities
  • IS support
UnnecessaryMotion

Unnecessary human movement (physical or user movement between tools or system)

Walking to information, retrieving printed materials
  • Lack of distributed, direct access
  • Lack of on-line access
  • Lack of digital versions of heritage information
Excessive keyboard, mouse operations
  • Lack of training
  • Poorly designed user interfaces
  • Incompatible software suites
  • Too much information to sort through
Poor physical arrangement or organization
  • Team members not co-located
  • Organization structure inhibits formation of right teams
Defects

Erroneous data, information, reports

Errors in data reporting/entries
  • Human error
  • Poorly designed input templates
Errors in information provided to customers
  • Lack of disciplined reviews, tests, verification
Information does not make sense to user
  • Raw data delivered when user needs derived information, recommendations, or decisions

Application

In order to build a value stream map in a coherent way, there are three main steps[2]:

  • Arrange the process steps (tasks) and information flows.
    • Follow the work: To uncover the true value stream, trap yourself to the product.
    • Collect the information yourself: Try to walk the process, talk to participants, have them send you examples of documents or information regarding what they produce and handle.
    • Exploit existing process information resources, cautiously: It is needed to understand the process personally but if someone helped collecting reliable data, use it.
    • Map "in pencil": Make process maps easy, low-investment, adaptable and simple formats.
    • Map the whole value stream: Have everyone work on the entire value stream and do not partition it right away. The goal is a holistic picture.
  • Collect performance data on the tasks, sometimes information flows as well.
    • Concentrate on what you need: If the problem is quality, look for errors and try to correlate them with their root cause.
    • Exploit what you can find: Sometimes the data is not the primary purpose of the document, instead it may be usefull dates on reports as a record for cycle time.
    • Make do with what you have: The data may be imperfect but if the data leads to the critical problem, it is usefull.
    • Be honest: Make data reliable by putting asside possible biases.
    • Dig deep (only) when you must: Only when analyzing critical problems and looking for solutions do further work collecting enough data.
  • Evaluate how value is created.
    • In detailed maps, specifically on lower level maps, non-value-added tasks may appear. Non-value-added activities may be hifing inside of value-added tasks, so try to add more detail to your map. Although this can lead to an unefficient way to find them, it is a good way to begin with. For deeper understanding about how to evaluate value refer to the related articles.

Some tools which are useful but were not intended for Value Stream Mapping will be described friefly[1].

  • Gantt Chart[7]: A traditional method for displaying sequence, schedule and dependency between tasks.
  • Process flow map[8]:Process maps to highlight waste and areas of improvement.
  • Learning to see: Most proven tool for lean base VSA/M. Refer to related articles for more information.
  • Design structure matrix (DSM)[9]: A well developed method for analyzing the sequences of, and information flows between, the tasks in a process.

Once the current state maps is complete, it is time to proceed identifying waste. This is the part when there is a vision of " the big picture " and everything is set to improve it. Since this tool comes form manufacturing principles, a re-interpretation of the main wastes has been performed. In manufacturing environments, the flow translates into physical materials while in project management it is information flowing instead. The seven info-wastes include:

  • Waiting: Late delivery of information; Delivery too early (leads to rework)
  • Inventory: Lack of control; Too much in information; Complicated retrieval; Outdated, obsolete information
  • Over-Processing: Unnecessary serial production; Excessive/custom formatting; Too many iterations
  • Over-Production: Creation of unnecessary data and information; Information over-dissemination; Pushing, not pulling, data
  • Transportation: Information incompatibility; Software incompatibility; Communications failure; Security issues
  • Unnecessary Movement: Lack of direct access; “Walking” the process
  • Defective Products: Haste; Lack of reviews, tests, verifications; Lack of interpretation (raw data delivered when information or knowledge needed)

The next table describes with examples each one of the seven info-wastes since it is very important to understand them in order to find on the state map.


Types of Information Waste Examples Causes
Waiting

Idle time due to unavailable information

People waiting for information
  • Lack of access
  • Untimely updating of data bases
  • Multiple approvals
  • Poorly designed or executed process to provide information
Information waiting for people
  • Information created too soon may be obsolete by the time it is used
Inventory

Information that is unused or is “work in progress”

Too much information
  • Poor understanding of user needs
Multiple/redundant sources
  • Tendency for everybody to maintain their own files
Outdated/obsolete information
  • Lack of “version control”
  • Lack of disciplined system for updating new and purging old information
  • Inadequate archiving standards or practices
“Just-in-case” information
  • Collection, processing and storage of every element of data that process participants can think of, whether or not a specific end use has been identified
Excessive Processing

Information processing beyond requirements

Excessive/custom formatting
  • Lack of standardization
Numerous, fragmented reports
  • Poor output design
  • Lack of understanding of the needs of the users of process outputs
Unnecessary serial processing
  • Poor system design
  • Lack of understanding of concurrent processing capabilities
Excessive approvals for information release
  • Stove pipe, command and control mentality
  • Turf protection
Over Production

Producing, distributing more information than needed

Unnecessary detail and accuracy
  • Tendency to “over-design”
  • More detail than necessary in early

design

Pushing, not pulling data, information
  • Uncontrolled process
Over-dissemination
  • Poor understanding of each

participant’s needs

  • “Send all information to everyone,”

rather than to meet specific needs

Transportation

Unnecessary movement of information between people, organizations, or systems

Information handled by multiple people before arriving at user
  • Lack of direct access due to IT system limits, organizational inefficiencies, knowledge hoarding, security issues
Information hunting
  • Lack of clear information flow paths, failure of process to produce information needed
Data re-formatting or reentry
  • Incompatible information types (drawings vs. digital descriptions)
  • Incompatible software systems or tools
  • Lack of availability, knowledge, or training in conversion and linking systems
Switching computers (e.g., CAD to PC) to access information
  • Software/hardware incompatibilities
  • IS support
UnnecessaryMotion

Unnecessary human movement (physical or user movement between tools or system)

Walking to information, retrieving printed materials
  • Lack of distributed, direct access
  • Lack of on-line access
  • Lack of digital versions of heritage information
Excessive keyboard, mouse operations
  • Lack of training
  • Poorly designed user interfaces
  • Incompatible software suites
  • Too much information to sort through
Poor physical arrangement or organization
  • Team members not co-located
  • Organization structure inhibits formation of right teams
Defects

Erroneous data, information, reports

Errors in data reporting/entries
  • Human error
  • Poorly designed input templates
Errors in information provided to customers
  • Lack of disciplined reviews, tests, verification
Information does not make sense to user
  • Raw data delivered when user needs derived information, recommendations, or decisions

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.[10]

Advantages

Limitations

Related Articles

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

Most of the VSM work that has been acomplished is around the manufacturing context. For practical implementation of VSA/M on manufacturing operations please refer to .[13]

Understanding how to break the PD process down into stages:[14]

Extensive understanding about how to proceed with Evaluation of Value: [15]

Rother and Shook's Learning to See a factory floor mapping which can be extrapolated to PD activities:[16]

Key references

  1. ↑ 1.0 1.1 1.2 1.3 1.4 1.5 1.6 http://dspace.mit.edu/bitstream/handle/1721.1/7333/Value%20Stream%20Analysis%20and%20Mapping.pdf?sequence=1
  2. ↑ 2.0 2.1 2.2 http://dspace.mit.edu/bitstream/handle/1721.1/81908/PDVSM_V.1_2005.pdf?sequence=1
  3. ↑ http://world-class-manufacturing.com/Kanban/kanban.html
  4. ↑ http://www.lean.org/Bookstore/ProductDetails.cfm?SelectedProductId=160
  5. ↑ 5.0 5.1 http://web.mit.edu/esd.83/www/notebook/WomackJones.PDF
  6. ↑ http://www.mbaskool.com/business-concepts/operations-logistics-supply-chain-terms/7409-value-stream.html
  7. ↑ http://apppm.man.dtu.dk/index.php/Gantt_Charts_as_a_Tool_for_Project_Management
  8. ↑ https://en.wikipedia.org/wiki/Flowchart
  9. ↑ https://en.wikipedia.org/wiki/Design_structure_matrix
  10. ↑ http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.201.6852&rep=rep1&type=pdf
  11. ↑ https://books.google.fr/books?id=7cCAASTW6IQC&hl=es
  12. ↑ https://books.google.dk/books/about/Principles_that_Shape_Product_Developmen.html?id=ZbYGtwAACAAJ&redir_esc=y
  13. ↑ https://www.amazon.es/Learning-See-Eliminate-Enterprise-Institute/dp/0966784308
  14. ↑ https://www.amazon.com/Product-Design-Development-Karl-Ulrich/dp/0070658110
  15. ↑ http://dspace.mit.edu/bitstream/handle/1721.1/81908/PDVSM_V.1_2005.pdf?sequence=1
  16. ↑ https://www.amazon.com/Learning-See-Stream-Mapping-Eliminate/dp/0966784308
Retrieved from "http://wiki.doing-projects.org/index.php?title=Value_Stream_Analysis_and_Mapping_for_Project_Management&oldid=29985"
Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox