Value Stream Maps

Updated 1 month ago by Copado Solutions


Copado's Value Stream Maps enables you to visualize the flow of value to end users. It is one of the core features included in DevOps 360. With Value Stream Maps you can get clear and actionable insights into your development process and identify any bottlenecks that may be preventing your team from delivering operational features in a reasonable time frame.

When talking about value stream maps, there are some concepts you should familiarize yourself with: stages, process blocks and metrics.

A stage represents a phase within the overall process you want to track. For instance, if you are tracking your development lifecycle, a stage could be ‘plan’ or ‘’develop’. You can define as many stages as you need. Each stage includes process blocks, which are specific processes within your stage. Considering the example above, a process block within the ‘plan’ stage could be ‘Design Review’ or ‘Sprint Planning’. As with stages, you can add as many process blocks as needed. Multiple process blocks in a stage are meant to indicate “parallel” processes. Finally, each process block contains metrics, which are quantifiable measures that provide key insights such as lead time or % complete and accurate.

Move on to the next sections to learn how to configure a value stream map and navigate the Value Stream Maps page.

Setting Up Your Value Stream Map

Before you build a value stream map, there are three things you need to configure beforehand, if you haven’t done so yet:

  • Enable My Domain in Salesforce’s Setup.
  • Enable chatter and feed tracking for Value Stream Map object. 
  • Add the Post action to Value Stream Map Layout.
  • Enable history tracking on at least one standard object and the object that you will be tracking, e.g. Account, User Story.
  • Enable field history tracking for any field you would like to use as the primary field in your Value Stream Map. This is required in order for Copado’s event collector to start tracking changes in this field and delivering metrics based on those changes.

For more information about all the adjustments you need to make prior to configuring your Value stream map, please check out the article Installation Instructions for Value Stream Mapping.

If you are upgrading from a previous version of Value Stream Maps, also check out the article Winter '21 Value Stream Mapping - Upgrade Instructions.

When building a value stream map, you first need to identify the stages that you would like to create. Once you have identified your stages, add process blocks associated with those stages  the value stream map with stages and then add process blocks to these stages.

To create a value stream map, follow these steps:

  1. Navigate to the Value Stream Maps tab and click on New.
  2. Give your value stream map a name.
  3. Select the object you want to associate your value stream map with.
  4. Select the primary field for your value stream map. Most objects within Salesforce have a field which measures the lifecycle of that object. For example, opportunities natively provide the Stage field.
  5. Select any record types that apply. You can select all record types or only one depending on your use case. You may want to focus on a particular record type, for instance if you want to track the progress or time your team spends on a particular type of user stories, bugs. In this case, you can select just this specific record type from the available options and move it to the Selected column. 
  6. Select a start date for your value stream map. If you have field history tracking enabled, the value stream map's event collector will utilize the field history tracking data to generate metrics based on the start date selected. If you do not select a start date, this field will be populated with the date that the value stream map is activated.
  7. Create as many stages as you need and drag and drop the boxes to rearrange them.
  8. Once you are done, click on Save:

Now that you have the object and primary field on which you want to base your value stream map, the date and the stages you want to track, you can go ahead and start adding process blocks to your stages. 

Creating Process Blocks 

To create a new process block, follow these steps:

  1. Click on the + icon at the bottom of the stage.
  2. Give your process block a name.
  3. If you selected all record types in the initial configuration of the value stream map, you now have the option to drill down and select a specific record type for your process block. If you don’t select anything, all record types will be included.
  4. Provide a description.
  5. Click on Save.

Configure Your Value Stream Map and Begin Mapping

Once you have configured all the process blocks you need, select the values and map them to the blocks. These are the values that will be analyzed and used to calculate the different metrics displayed in each process block. You can map more than one value to a process block. You will find values from the primary field that you selected in the creation of the value stream map on the right hand side panel. The drag and drop interface enables you to drag values from the right to the stages and process blocks on the left:

By default, all stages include a Waiting Time section at the top where you can define what is considered a waiting criteria. Below the waiting criteria, you will find active criteria. 

Once you complete the mapping and are ready to save the value stream map, you have two options:

  • Save Configuration: Save your Value Stream Map but do not activate it yet.
  • Save & Activate: Use this option if you want to activate your value stream map straightaway.

To review the value stream map you have just created, navigate to the Value Stream Map tab click on the Value Stream Map record you would like to navigate to. You will be taken to the Value Stream Map’s main page:

Metrics and Icons

On this page you can find five key metrics at the top:

  • Rolled % C/A: This metric displays the percentage of work items that pass through all the stages without having to be sent back to prior stages due to quality issues. It is a product of the weighted % C/A.
  • Total Cycle Time: Cycle time represents the time that was spent on completing a work item for a process block (excluding the idle time). Total cycle time is the sum of average cycle time for a work item to complete a process, that is, the sum of cycle time across all stages.
  • Total Idle Time: Average time that a particular work item will spend waiting before it is completed.
  • Total Lead Time: The sum of lead time across all stages.
  • Total Work in Progress: The number of work items that are currently in progress.

Below the top-level metrics, you will find all of the process blocks you have created which include several metrics. Let’s take a look at the icons and metrics included in a process block:

  1. This icon shows historical idle time, which represents the average time a work item spends in the waiting section at a specific stage.
  2. This icon displays the current number of work items that are in a waiting status at a particular stage.
  3. This icon shows the current number of work items that are in an active criteria in a process block.
  4. This icon shows the current number of unique owners across all work items in the process block.
  5. Lead time: The average time it takes for a work item to be completed in a process block + waiting time (historical).
  6. Cycle time: Cycle time represents the time that was spent on completing a work item for a process block (excluding the idle time).
  7. % C/A: Percentage of work that was completed without a re-entry to the process block.
Copado uses historic work items to estimate current work in progress. Some metrics such as the lead time and the % C/A within process blocks are historical averages.


Create Custom Metrics

On this page you can perform the following actions:

  • Create custom metrics at the top by clicking on the + sign:
    Select the field you want to measure and the calculation type. The available calculation options are SUM and AVG:

  • Sort, edit or delete a custom metric by clicking on the drop-down menu next to each custom metric:

Create a filter to see data for a specific date range or filter by other fields included in the object selected for the value stream map. Applying a filter will automatically adjust the standard and custom metrics:

You can now use the contains filter logic or build a filter based on a picklist field.

Interactive Icons
  • Click on any process block or stage to see the underlying records and navigate to the data displayed on the stage or process block.

View, Edit, & Configure
  • Click on Edit Details at the top right corner to edit your value stream map.
  • Click on Configure Value Stream Map at the top right corner to edit the process blocks and the mapping. From there, you can cancel the changes, save the configuration or save and close to go back to the main page.
  • Select View Value Stream Details from the drop-down menu to navigate to the Value Stream Maps record.


To deactivate the value stream map, select Deactivate from the drop-down menu at the top right corner.

  • Recalculation can be required if you are making any changes to your value stream map configuration, stages, or process blocks. This can be required due to changes in the value stream maps mapping. 
  • Recalculation works as a refresh of the data since the value stream map has an event creation batch that runs every hour. Running a recalculation will give you new value stream maps metrics based on the last time the value stream map was recalculated.
  • Select Recalculate from the drop-down menu at the top right corner to manually recalculate your value stream map and see the latest metrics related to your value stream map.


You can now use chatter in the value stream map to collaborate with other teammates on your work items and discuss improvements for your processes based on the metrics displayed on the value steam map.

How did we do?