Value Stream Analysis and Mapping for Project Management

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). Value Stream Analysis and Mapping (VSA/M) is a tool for business process improvement. 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. 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:

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:

• 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:

• 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 flow. Also to move the processes towards a more rapid response for customer pull. On a product development context, this means rapid response towards customer needs when it comes either to new products or permutations of the existing ones.

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. A number of techniques are then applied once cathegorised these types of waste. Which in the lean manufacturing pcontext include manufacturing cells, Just-In-Time deliveries, aparts supermarkets, etc... Once established the future state map, it is implementet 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 Program Management environment

According to the product development team at MIT's Lean Aerospace Initiative, the value of the Product Development (PD) process 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 PD value stream, like the manufacturing value stream is done. This way fitting with other activities around the business cycle to define an overall value as we can see on the Figure 2.

Figure 2: PD Value Context - Source:

In order to extrapolate the VSM under manufacturing principles to a Program Management environment, how does the flow thorough the PD process translates into? In this case it is information. Information flows thorough the PD process like on the manufacturing environment material does. The quality of the information flow is characterized by its Form, Fit, Function and Timelines (FFFT). However, PD 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 PD process, tasks add value to the information. Since the flows in PD are made of information instead of physical materials. Using the next seven info-wastes should enable to identify wastes associates with the information flows:

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 up a value stream map in a coherent way, consider three main steps:

• 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.

• Gantt Chart: A traditional method for displaying sequence, schedule and dependency between tasks.
• Process flow map: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): 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 the manufacturing environment the flow translates into physical materials while in PD its information which flows 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)

On the previous table about types of information waste on the methodology part there are examples and causes. The point about having a large list describing examples about each one of them is because it is very important to understand them in order to find them on the state map.

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.

Related Articles

The lessons from Toyota for product development had been captured by Fujimoto and Clark and Ward and Sobek. 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 .

Understanding how to break the PD process down into stages:

Extensive understanding about how to proceed with Evaluation of Value:

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