Clarity: Top-Down Planning with Roadmaps

ccppmop1593
HID_newux_roadmaps
Sid is a portfolio manager and manages a large portfolio of investments and assets. He needs to understand the big picture because he is responsible for funding and headcount alignment across the portfolio.
Roadmaps
Sid provides insights for strategic pivots, to ensure the company is delivering superior outcomes based on solid business decisions. His biggest worry is that customers are growing more discerning and competitors are more disruptive. This means that from a planning perspective, he needs to accelerate the pace and puts pressure on organizations to make everything a “top priority.” Hence, organizations are overcommitted and investment plans are driven by operational backlogs rather than a shared strategic vision.
He realizes that to transition from traditional project management to digital product management he needs 360-degree visibility into all the components, including hardware, software, services, and processes, underpinning digital products developed and maintained by his teams. He has three key requirements to help him transition from traditional project management to product management:
  • The planning process should be quick and easy: Traditional investment planning requires users to articulate projects at a far too granular level just to get started, leading to organizational fatigue or even an absence of meaningful planning.
  • Every work item and investment needs to be mapped to organizational strategy: Most teams start by aligning to the strategy but deviate significantly as other priorities start competing for their time.
  • All stakeholders need a single integrated view of the strategy and plans: Stakeholders need a method to visualize, communicate and gain consensus around a proposed set of objectives. That means they need the ability to analyze new initiatives alongside work that is already planned or underway
Sid can use
Clarity
's powerful Roadmap capabilities to meet the needs of many stakeholders involved in strategic management and planning. There is no limit to the number or types of roadmaps that can be created in the
Clarity
system.
For example, stakeholders might include product, architectural, or feature roadmaps, or any other roadmaps required by an organization. Each agile roadmap includes multiple different views including a timeline view, a board view, and a grid view. You can toggle from one view to the next to access the information they need and easily save personalized views.
Additional Resources:
2
Prerequisites
To use Roadmaps, verify with your administrator that the following configuration is complete in
Classic PPM
:
  • Create a default entity
    . See
    Create an Entity
    in Configure an Organizational Breakdown Structure.
  • Configure monthly, quarterly, and annual fiscal time period types for the default entity
    . See Set Up a Financial Entity. If any fiscal period types are not defined on the default entity, those fiscal period types are blank in the column headings in the timeline.
  • Grant users the required access rights
    . See
    Clarity
    Access Rights Reference
    in the English edition of the documentation.
  • Create custom global picklists
    . Include the grouping attributes or lookup values that your organization wants to use in all roadmaps. See Create a Custom Global Picklist.
  • Configure color display mappings
    . You can customize the color grouping options available for the default global picklists. You can also assign color grouping options for your custom global picklists. See
    Clarity
    Studio Objects and Attributes
    in the English edition of the documentation.
Review a List of Existing Roadmaps
Login
You can use the Roadmaps page to create a new roadmap for your organization. Since the Roadmaps page utilizes the
Clarity
common grid some of the key actions you can perform are:
  • Use the Column panel to customize the grid by adding various fields to it
  • Filter the data in the grid based on your business requirements
  • Use the Group By option to collapse related rows view aggregated subtotals wherever applicable
  • Export the various roadmaps along with the data in the grid to a CSV file
  • Add custom attributes to the grid layout, the column panel, and filters
  • Edit data associated with roadmaps directly in the grid or by using the DETAILS layout
  • Save your view
For more information on how you can leverage the generic grid capability of
Clarity
, see Common Components
Create a Roadmap
You can use the Add Row icon or the New Roadmap button to create a new roadmap.
Follow these steps to create a new roadmap:
  1. Log into
    Clarity
    and click
    Roadmaps
    .
  2. Click
    New Roadmap
    or click the Add Row Icon
  3. Complete the following fields:
    • Roadmap Name
      Enter the name of the roadmap.
    • Author
      This option is not displayed if you are using the New Roadmap button. If you are using the Add Row icon to create a roadmap, you can select the relevant author by using the Author field.
    • START PERIOD
      Defines the roadmap start period that is based on what fiscal annual periods you have configured for your default entity. The field shows the next fiscal annual period by default. For example, if the current date is April 15, 2021, the default fiscal period shows 2022, the next annual fiscal period. 
    • DURATION
      Defines the roadmap duration and shows one year as the default. The duration that you can select depends on the corresponding annual fiscal periods that are set up on the default entity. For example, you select 2020 as the start period and there are three annual fiscal periods (2020, 2021, and 2022) set up on the default entity. The duration options that appear include 1 Year, 2 Years, and 3 Years.
      The
      Other
      option appears if you have more than five annual periods that are defined in the future. Consider a scenario where you select 2020 as the start period and the default entity has annual fiscal periods that are defined through 2028. In such a scenario the
      Other
      option appears. When you select this option, the system allows you to enter only a number from 6 through 8. You can change the duration after creating a roadmap by updating the
      Duration
      attribute.
  4. Click
    CREATE
    .
    Your new roadmap appears in the default timeline layout with a unique system-defined ID. If auto-numbering is not set up in
    Classic PPM
    , enter a unique ID for your roadmap.
  5. Add items to your roadmap in the timeline, board, or grid layout.
To delete a roadmap, from the Roadmaps list page, select the roadmap and click
Delete
.
Edit Roadmap Details
You can add more details to your roadmap such as
description
or
type
. You can also edit the existing details. For example, change the author from you to somebody else who can take ownership of it.
Follow these steps:
  1. On the Roadmaps page, use the column panel to add relevant attributes to the grid. You can add attributes such as Description, Type, Status, and Starred.
  2. Enter the values associated with various attributes to add or edit details associated with the roadmap.
You can also use the Properties tab within a roadmap to edit the various roadmap details.
Add Roadmap Items
A roadmap consists of items that you want to plan during a given time such as an annual business event or a project that spans multiple quarters. Multiple roadmap items fill the roadmap duration.
You can build a roadmap by adding items as you work through the planning details and funding constraints at your organization. You can use any layout to add roadmap items. When you revisit an existing roadmap, the application returns you to the most recent layout for that roadmap.
You can create roadmap items in
Clarity
by using one of the following methods:
  1. Use the Add Row button on the Timeline, Grid, or Board layouts to create a new roadmap item.
Note
: If you are using scenarios, a roadmap item is only added to the currently selected scenario in which you are working, not to all existing scenarios.
Import Roadmap Items From a CSV File
Sid is a Portfolio Manager and his product teams currently use spreadsheets to plan their product launches. Let’s help them quickly create a roadmap by importing their data into
Clarity
.
You can import a list of up to 250 roadmap items from a comma-separated values (CSV) file. Your imported roadmap items appear inside a single roadmap scenario. You cannot update existing roadmap items with this feature.
Importing roadmap items requires the
Roadmap - Edit
instance-level or OBS-level access right or the
Roadmap - Edit - All
global access right.
Refer to the following table for the supported types of roadmap item attributes that you can import and their correct formats.
Attribute Type
Format
Numbers
Do not use a thousand separator. Enter periods for the decimal places. Use a dash for negative numbers.
Percentages
Enter percentages as decimals. For example, to import 25percent, your raw import row should show 0.25.
Monetary values
Do not include a comma for the thousands separator, unless you enclose it in quotes. Decimal values are acceptable; however, do not include currency codes or symbols.
Strings
Use double quotes around any strings with commas. For example, "Roadmap Item 1 for regions A, B, and C".
Dates
Use the YYYY-MM-DD format. For example, 2019-11-15 for November 15, 2019.
Static single value lookups
Specify one case-sensitive value from the set. For example, for type specify
Project
,
Program
,
Idea
, or
Feature
. For inPlan, specify
2
(In Plan) or
1
(Not In Plan).
Follow these steps:
  1. Log in to
    Clarity
    .
  2. In the main menu, click
    Roadmaps
    .
  3. Open a Roadmap and on the Roadmap Items tab select a scenario.
  4. Click
    Item Actions
    ,
    Import from CSV
    .
  5. Download the PPM_ROADMAP_CSV_IMPORT_TEMPLATE.csv file.
  6. Prepare the CSV file:
    1. Open a spreadsheet, database, or other application where you can format your source CSV file. For example, a committee decides to explore 40 new portfolio items and sends you a list. You can configure that list in Microsoft Excel. Save a copy of the import template as my_new_items.csv, paste your list of 40 items, format the list as required, and import it into
      Clarity
      .
    2. Review the first row of the template. The first row contains optional user-friendly names and instructions for each field. For example, Roadmap Item Name (Required field - Max = 80 characters), Start Date, NPV - Net Present Value (Money +/-0.00), or Operating Cost (Money +/-0.00).
    3. Verify that the second row contains the
      API Attribute ID
      for each attribute. The default values are already set. Your administrator can change these IDs in
      Clarity
      Studio. For example, name, start, npv, or operating cost. You can change the API Attribute IDs for any custom attributes only.
    4. Verify that the remaining rows (up to 250) contain values that are delimited by a comma with no spaces. Excel handles the commas inside cells and between cells for you when you save as CSV. You do not see the commas in Excel. You can build a raw import file in text using Notepad where you must include the commas.
    5. Verify that any date values you want to import follow the YYYY-MM-DD format. Be careful that Excel does not reformat your values.
    6. Save your CSV file. If working in Excel, use the Save As option to save your file as a CSV file with the .csv file extension.
  7. Verify that you have opened a roadmap and selected a scenario.
  8. Click
    Import CSV
    .
  9. Select the CSV file from your local PC or network server and click
    Import CSV
    .
    A confirmation message shows you how many rows were successfully imported and how many rows could not be imported.
  10. Locate your new imported roadmap items on the board, timeline, or grid. On the board, imported roadmap items might appear in the
    None
    column, ready for you to review. On the timeline, imported roadmap items appear in their specified swim lane (for example,
    None
    ,
    Project
    , or
    Idea
    ).
New items may not necessarily appear in the NONE column. Their placement depends on how the data is set up in the CSV. You could specify a lookup value for the status or type. The roadmap item would appear in the column or swimlane that corresponds with that value.
When working with the CSV import template in Microsoft Excel, observe the following requirements:
  • Format date column cells with the custom YYYY-MM-DD format.
  • Do not use commas as thousands separators.
  • Save the file as CSV and use UTF-8 encoding to preserve special characters that extend beyond the standard ASCII (ISO 8859 Latin I) codeset.
Use the following images for guidance:
csv.jpg
Import Projects, Custom Investments, and Ideas from
Clarity
You can create roadmap items by importing active projects, ideas, or custom investments for which you have at least view access rights. When you import projects, ideas, or custom investments as roadmap items, the application creates a link between the roadmap item and the investment object. Each investment object remains linked to the new roadmap item.
The Import from
Clarity
option now displays the corresponding grid with selection checkboxes. You can select Projects, Ideas, or Custom Investment Items from the respective grid. The selection grid lets you select individual row items. You can also select or deselect all rows.
You can select any number of investments from the grid.
Clarity
imports the selected investments. The Select all Option lets you select all the line items to import in an instant.
import investment objects from grid
You cannot import a project, idea, or custom investment that is already linked to a roadmap item in a scenario. Those projects, custom investment, and ideas are excluded from the IMPORT FROM
Clarity
drop-down.
Before you can link a roadmap item with a project, idea, or custom investment, ensure that the following conditions are met
  • They are
    active.
  • The project is not a template or program.
  • The
    Include in Roadmaps
    setting for the custom investment type is selected.
  • The custom investment is not already linked to another roadmap item in the same roadmap scenario.
When the start and finish dates of a project is different from that of the associated cost plan of record, the start and finish dates of the linked roadmap item reflect the project dates. However, financial attributes such as Capital Cost or Operating Cost reflect the data from the cost plan.
Follow these steps:
  1. In the main menu, click
    Roadmaps
    .
  2. Open a roadmap in the timeline, board, or grid view.
  3. Click
    Scenarios
    , and select a scenario.
  4. Click
    Item Actions
    and select
    Import from PPM
    .
  5. To import any investment object, complete the following steps:
    1. Select
      Project, Idea, or <custom investment name>
      from the drop-down menu.
      The
      Select From page appears.
    2. Select the checkboxes corresponding to the rows.
    3. Click
      Add
      .
      Each imported project or investment appears as a roadmap item in the timeline, board, or grid. Roadmap item data remains linked to the original projects and investments. The Linked To and Linked To ID columns on the grid layout show the original project or investment data. The financial data from the cost plans of the imported custom investments is also imported in the roadmap item.
    4. You can import investment objects linked to an OBS unit or import multiple individual investment objects.
  6. (Optional). Click the Linked To column item and view the instance details.
  7. (Optional) Save any special changes that you make to the current scenario and view.
Link Roadmaps Items to Projects, Custom Investments, and Ideas
In a roadmap scenario, you can associate a roadmap item to an existing project, a custom investment, or an idea. You will only see projects, custom investments, or ideas for which you have at least view access rights. If you are linking Roadmap Items to a project, then the project:
  • Should be active
  • Cannot be a template or a program
  • Should not be linked to another roadmap item in the same scenario
Similarly, once an idea or a custom investment is linked to a Roadmap item, they cannot be associated with other roadmap items.
Linking allows you to drill into the associated
Clarity
object (project, custom investment, or idea) and view more details about it. Also, you can import the latest system data from the object into the roadmap item.
Linked
Follow these steps
  1. Open a roadmap.
  2. Click
    Scenarios
    to select a scenario.
  3. If you are on the Grid layout, use the
    Linked To
    column to link the roadmap item to a project, an investment, or an idea. 
    1. The
      Linked To ID
      column is automatically populated with the linked project or investment ID.
    2. The
      Linked to Type
      column is automatically populated based on the type of imported object (project or custom investment type).
    If you cannot see the Linked To or any other columns in the grid, use the Column Panel to add columns to the grid.
  4. In the Timeline or Board layout, select the roadmap item to open the DETAILS panel.
  5. In the Linked To option, select the project, custom investment, or idea you want to link to the roadmap item.
  6. Click
    Done
    to save your changes.
  7. Use the hyperlink to access the project, investment, or idea pages. Depending on the object type you linked and the type of access you have, you land on one of the following pages:
    • Project tiles page
      : You land on the project tiles page when you have access only to the project but no access to any of the modules (tabs) configured in the project. Consider an example where a project is configured to include only the Risks, Issues, and Changes modules. If you have view access to this project but no access to any of the modules, you land on the project tiles page. You do not see a link to navigate back to the source roadmap.
    • Project page with error
      : You land on a project module page and receive an unauthorized error. Consider an example where a project is configured to include only the following modules in the listed order: Tasks, Risks, Issues, and Changes. If you have view access to this project but no access to the first module (Tasks), you land on the Tasks page of the project. However, since you are not authorized to see tasks, you get an error on the page. You see a link to navigate back to the source roadmap. You do not see any other modules.
    • Project page with no error:
      You land on a project module page and do not receive an error. For example, a project is configured to include only the following modules in the listed order: Tasks, Risks, Issues, and Changes. If you have view access to this project and also access to the first module (Tasks), you land on the Tasks page of the project. You are also able to see the tasks and a link to navigate back to the source roadmap. You do not see any other modules besides Tasks.
    • Investment Details page
      : You land on the investment details page.
    • Idea Details page:
      You land on the linked idea's grid page.
  8. To navigate back to the roadmap, click the roadmap name link at the top of the page.
You can also delete the link between roadmap items and
Clarity
objects.
Follow these steps
:
  1. Open a Roadmap.
  2. Click
    Scenarios
    and select a scenario.
  3. If you are on the Grid layout, click the Edit icon on
    Linked To
    column and click
    REMOVE LINK
    . You can also select the Roadmap item, open the DETAILS panel, click the Edit icon and select Remove Link.
  4. In the Board layout or Timeline layout, select the roadmap item and open the DETAILS panel.
  5. Click the
    Edit
    icon next to the linked
    Clarity
    object.
  6. Click
    Remove Link
    .
  7. Click
    DONE
    to save your changes.
Synchronize Roadmap Items with Linked Project, Custom Investment, or Idea Attributes
Links are created between roadmap items and projects, custom investments or ideas when you perform the following actions:
  • Import projects, ideas, or custom investments into a roadmap.
  • Link a roadmap item to a project, idea, or custom investment in the grid.
As the roadmap or portfolio manager, you can synchronize your linked roadmap items to existing projects. Synchronizing ensures that the roadmap data reflects the latest system data from the linked projects. You can control which roadmap items, attributes, or attributes groups to synchronize. As a project manager, Nicole should also be able to sync either Allocation based or Assignments based capacity attributes.
  • You can only synchronize the system-defined roadmap items and attributes (metrics and dates) that are available by default.
  • If the parent of a project contains custom attributes that match the API Attribute ID of a roadmap item, the value of the attribute is synced when the project is synced.
  • The following financial attributes (planned and actual) can carry over and can remain synchronized with each imported object:
    • Currency Type
    • Payback Period
    • Benefit and NPV (Money)
    • Capital Cost, Operating Cost, and Total Cost (Money)
    • IRR and ROI (Percent)
  • You have the ability to sync Capacity as either Allocations or Assignments.
    • Syncing Allocations enables the roadmap owner to understand the total capacity planned for a roadmap.
    • Syncing Assignments enables the roadmap owner to understand the total capacity committed and the remaining capacity for a roadmap.
    • If you select Assignments, Capacity values derived are ETC + Actuals.
    • If you select Allocations, Capacity values derived are Allocations.
    • Clearing the Capacity checkbox disables Assignments & Allocations options. By default Allocations option is selected.
The sync functionality is identical for Projects, Ideas, and Custom Investment Types. In
Clarity
15.9.2 and higher releases, you can synchronize rich text fields between various investments and roadmaps.
Example:
Sid is working in a roadmap grid that has several roadmap items that are linked to
Clarity
projects. As the portfolio manager, Sid knows that there are several project managers still working on changing metrics in their projects. He wants to exclude these projects from the synchronization process. Sid wants to control which roadmap items are updated with the project data. He also wants to update only the actual attributes and not the planned ones. When the project managers are done updating their plans, Sid opens the roadmap, selects the remaining roadmap items, and synchronizes them with the latest project data.
Follow these steps:
  1. In the main menu, click
    Roadmaps
    .
  2. Open a roadmap in the grid.
  3. Click 
    Scenarios
    and select a scenario.
  4. Import projects, ideas, or custom investments into a roadmap or link a roadmap item to a project, idea, or custom investment in the grid. Verify that the Linked To field shows the associated project, idea, or investment.
  5. Click 
    Column Panel
    and select one or more custom attributes that you want to synchronize in the grid.
  6. Select the
    Sync
    attribute. You might have to scroll the grid to the right to view the new attribute in its own column. By default, syncing is selected for linked roadmap items.
  7. For the linked roadmap items that you do
    not
    want to synchronize, clear the checkbox in the
    Sync
    column.
  8. Click 
    Item Actions
    and select
    Sync Linked Items
    .
    1. Select the roadmap item attributes to synchronize. You can select all attributes, attribute groups, or only specific attributes.
    2. To sync custom lookup attributes for projects, ideas, and custom investments select
      Matching Custom Attributes
      .
    3. Click
      SYNC
      .
      Sync in progress
      appears. You can work on other scenarios or other application pages during the sync operation. Only the current scenario is temporarily locked for editing.
  9. After the sync process is complete, the custom attributes are populated in the roadmap item custom attributes.
    When you sync roadmaps with projects, you can select between syncing allocations or assignments. If you select assignments,
    Clarity
    will use add the ETC and the Actuals for the project to calculate assignments and synchronize the project with the roadmap. When you import a project as a roadmap all the relevant data associated with the project is imported as roadmap attributes. When you synchronize a roadmap, it only updates the attributes you selected in the Sync Linked Items window. In Clarity 15.9.3 and higher releases, you can sync the Roadmap Item Name with the "Name" of the linked investment.
    Group By.jpg
Matching Custom Attributes
When synchronizing matching custom attributes, the match is based on the API Attribute ID and Data Type for the child attribute of the parent Project, Custom Investment, or Idea object:
  • The API Attribute ID and lookup data type for the attribute must match the API Attribute ID of the roadmap item object.
  • The type for the attribute must match the attribute type on the roadmap item object.
  • The lookup must also match.
The following conditions also apply:
  • API Attribute ID must be a single character followed by an underscore (example: c_attribute).
  • When you select the
    Matching Custom Attributes
    option and the application finds a match, the data from the investment populates the roadmap item.
  • If the application finds no matching attributes, nothing happens to your custom investment attributes. The application continues synchronizing the remaining linked items as usual.
Synchronization is supported for custom attributes with the following datatypes:
  • Lookups (SVL) - (Static and Parameterized)
  • Number
  • String
  • Boolean
  • Date
  • Money
  • Large text
  • Clarity
    will synchronize additional attributes when you select the "Matching Custom Attributes“ option.
  • Clarity
    matches attributes based on API Attribute ID and type.
  • If you select the "Matching Custom Attributes" option and
    Clarity
    finds a match based on these criteria, the data will be populated from the investment to the roadmap item.
  • When you synchronize Large String attributes,
    Clarity
    will copy the data as is, including special characters and formatting.
  • When you synchronize the “Money” attribute,
    Clarity
    will copy the amount without any conversion.
  • When you synchronize the “Money” attribute,
    Clarity
    requires two pieces of information namely currency and amount.
Sync Column and Checkbox
The following three conditions control the appearance of the
Sync
checkbox in the grid:
  • Visible and Not Selected
    : The roadmap item is linked to a project; however, you do not want to synchronize it.
  • Visible and Selected
    : The roadmap item is linked to a project and ready for synchronization.
  • Not Visible
    : The roadmap item is not linked. Without a linked project, the roadmap item cannot be synchronized.
To identify the last time a roadmap item was synchronized, add the
Last Synced Date
field from the Column Panel to the grid.
Manage Roadmap Picklists
Configure a Default Global Picklist
The default picklists for grouping roadmap items are based on the values that your administrator defines for the following lookup attributes. The lookups reside on the Roadmap Item object in
Classic PPM
:
  • Status
    : The lookup contains the values for the Status attribute that lets you group items into columns by status. For example, all unapproved roadmap items appear under the Unapproved column.
  • Type
    : The lookup contains the values for the Type attribute that lets you group items by roadmap item type. For example, all ideas appear under the Idea column.
The In Plan lookup attribute is system-restricted. You cannot customize the lookup to add more values. You can only change the labels and the display colors for the existing values.
The default picklists are global and are available to all roadmaps in the system for grouping roadmap items. They appear differently on the different layouts. On the timeline layout, they appear as swim lanes with optional colors. On the board layout, they appear as columns with optional colors. On the grid, they appear as columns.
If a default color is not defined for the picklist values, the application uses white as the default color. You can customize the default color for the default global picklists.
Work with your system administrator to configure the default global picklists in
Classic PPM
. See
Clarity
Studio Objects and Attributes
for details.
Follow these steps:
  1. Click
    Administration
    ,
    Studio
    ,
    Objects
    .
  2. Open the Roadmap Item object and click the
    Attributes
    tab.
  3. Select the attribute that you want to configure. For example,
    Status
    ,
    Type
    , or
    In Plan
    .
  4. Configure the following properties:
    • Set the order in which the values appear in the list.
    • Rename or add values to the list to align with your business needs.
    • Change the predefined color display mappings.
    • Activate a lookup picklist that was previously deactivated or deactivate a lookup so it no longer appears as a picklist.
      Users cannot add new picklist values to the columns for deactivated picklists. The column appears visually different compared to the active columns. When you move the last item out of the deactivated value column, the column disappears.
  5. To add a new global picklist, click
    New
    and define the roadmap item attribute and its values.
Do not be confused by the appearance of a field called
Type
with values such as Investment, Product, and Application on the Details panel, and another field also called
Type
with values such as Project, Program, Idea, or Feature as seen in the swimlanes and legend. You are seeing the subtle difference between
Roadmap Type
and
Roadmap Item Type
.
Create a Custom Global Picklist
You can create your own custom picklist containing custom grouping values that are governed by the company. The global picklists appear under the SWIMLANES or COLUMNS and COLOR BY list under
All Roadmaps
. They apply to all roadmaps.
For example, you can create a custom picklist that is named Business Outcomes to group your roadmap items using the following values:
  • Mobile
  • Technology Enhancement
  • Wow the Customers
The custom picklist becomes available in the Columns and Color By grouping attributes. You can then select Business Outcomes from the Columns attribute to view your roadmap items that are grouped into columns corresponding to their business outcome value. Also, you can select Business Outcomes from the Color By attribute to view your roadmap items that are grouped by colors that you associate with the business outcomes.
Follow these steps
:
Note
: Work with your system administrator to configure a global picklist in
Classic PPM
using the following high-level steps. See
Configure Lookups
under
Administration
for details.
  1. In the Administration tool, create a Static List lookup that is associated with the Roadmap Item object. Select the Manual sort order so you can define the order in which the lookup values appear on the UI.
  2. Add your custom values to the lookup. The values correspond to the grouping options that the picklist contains on a roadmap.
  3. Reorder the values manually.
  4. On the Roadmap Item object, create an attribute. The attribute name corresponds to the picklist name that displays on the roadmap.
  5. Associate the new attribute to the Static List lookup using the Data Type field.
  6. In Display Mappings, select a color to represent each lookup value.
  7. (Optional). Specify a default color for each lookup value. If you deactivate a lookup value, the assigned color disappears for the value from the roadmap and it displays in the default color.
When you create a global picklist, the existing roadmap items first appear in the None swim lane or column and are sorted by their start date. You can then move these items from None to the other lanes. If you deactivate or delete the picklist in
Classic PPM
, the items again appear in the None swim lane or column.
If you delete the roadmap Item attribute that is used as a custom global picklist, the picklist is removed from all roadmaps.
Create a Local Picklist
Create a local picklist to group roadmap items by columns or by color in a specific roadmap. You can then use the picklist across all the layouts. For example, if you create a Columns picklist in the Board layout, the picklist appears in the Timeline settings as an option under SWIMLANES. In the Grid layout, the picklist choices appear in the Column Panel.
Apply the picklist choices to the roadmap layout. For example, if you create a columns picklist, move any new roadmap items from the None column to the new columns.
Follow these steps:
  1. Open a roadmap and click
    Timeline
    ,
      Board
    ,
    or Grid
  2. Click
    View Options
    .
  3. Click
    MANAGE PICKLISTS
    .
    The MANAGE PICKLISTS window appears.
  4. Click
    NEW PICKLIST
    .
  5. Enter a picklist name (for example, Business Outcomes).
  6. Add choices to your picklist. Name the choices to correspond to your picklist values. For example, Mobile, Technology Enhancement, and so on.
  7. To select a color for a picklist choice, click the red box to the left of the choice. Pick a color from the palette that displays.
  8. Click
    Done
    to save the picklist and add it to the Columns or Color By list under
    THIS ROADMAP
    .
If you create a color picklist, a color legend appears at the bottom right corner of the page. The legend displays the colors and their corresponding values in the picklist.
Example:
Sid has already compiled a roadmap of the new efforts that his research teams have underway. Upon drilling into the roadmap, Sid realizes that he wants to group the roadmap items by team, which is not a currently defined grouping available. He creates a Team picklist for his five teams, then distributes the available roadmap items to those teams. He also wants to have a quick way to indicate the status of these items. Sid selects Status as the color by attribute, which also causes a legend to appear at the bottom of the page indicating which color reflects which status. He then saves these choices as part of his "Working View".
NOTE:
When you switch between different scenarios for a roadmap, the grouping that you have currently selected for the roadmap items remains the same across all the scenarios.
Manage Local Picklists
You can select an existing local picklist or search for a picklist by name. After selecting a picklist, you can edit or delete the values. If you delete a custom local picklist that is applied to a roadmap view, the default picklist gets applied to the view. For example, say that you have selected a local picklist (MyPicklist01) for the Columns grouping on the board layout. You delete the picklist. The view then refreshes and applies the default global picklist of Status to the Columns grouping.
Follow these steps:
  1. Open a roadmap and click
    Timeline
    ,
    Board
    , or
    Grid
    .
  2. Click
    View Options
    .
  3. Click
    MANAGE PICKLISTS
    .
    The MANAGE PICKLISTS window appears.
  4. Select a picklist that you want to edit.
  5. Edit the picklist values as follows:
    • Rename, delete, or add choices.
    • Move the choices up or down in the list.
    • Change the color choices.
    • Delete the entire picklist.
  6. When done, click
    X Close
    .
Delete a Local Picklist Choice
  • If you delete a picklist choice, the corresponding column or swim lane is deactivated and appears unavailable on the layouts. After you move all the roadmap items from the deleted column or swim lane, the column or swim lane disappears.
  • If you delete a picklist choice that is assigned a color, any existing roadmap items continue to display the color. After you move the roadmap items from the deleted column or swim lane, the column or swim lane with color disappears.
Create Roadmap Planning Scenarios
A scenario is a copy of the roadmap data with a unique name. Scenarios allow you to explore changes to the roadmap items in the context of a
what-if
scenario. For example,
how can we maximize ROI
?
What if we add 50 resources? What if we increase the contractual price to our client and delay shipping for six months?
You can create multiple scenarios for a roadmap and can indicate which is the plan of record and which is the baseline. When you report the portfolio performance, you can decide to use only one plan (for example, the plan of record).
Example:
Sid is preparing for a stakeholder meeting to review his Technology Work roadmap for the next six months. The stakeholders ask many questions. He wants to answer them visually so they can see the impact of making the suggested changes. For example, John wants to know if adding more resources for the roadmap items delivers faster time-to-market. Karen wants to know the impact if they reduce funding and allocate fewer resources. Sid selects the default scenario and clicks Save As to create a scenario with a new name. He edits the content to reflect these scenario questions. Sid creates the following scenarios from the default scenario:
  • Technology Work with More Resources
  • Technology Work with Fewer Resources
As you switch between scenarios, only the roadmap item data changes. Everything else remains the same including the view personalizations and the grouping.
Follow these steps:
You can create a scenario from any roadmap layout by copying either the default scenario or an existing scenario.
  1. Open a roadmap and click
    Scenarios
    .
    If you have not created any scenarios, the Default Scenario appears in the Scenario drop-down list. If you have created scenarios, the existing scenarios also appear on the menu.
  2. Select the default or an existing scenario and then select
    Save As
    to create a copy of that scenario.
  3. Enter a name for the new scenario and click
    Save
    .
  4. Edit the roadmap items specific to this scenario. The changes are not reflected in other scenarios.
Default scenario
If you are not using scenarios, the system creates a default roadmap scenario using the base roadmap data and applies the Plan of Record (POR) tag. Until you create more scenarios, the default scenario and its POR tag are not visible.
Baseline
You can tag only one scenario per roadmap as a baseline. You are not required to mark a scenario as a baseline. If a scenario is already tagged as the POR, you cannot tag it as the baseline. You can delete a roadmap scenario that is the baseline.
Plan of Record (POR)
You can tag only one scenario per roadmap as the plan of record. If no scenarios exist for a roadmap, you cannot edit the default scenario plan of record tag to No. There must always be a plan of record scenario in the system. If you try to delete a roadmap scenario that is the plan of record, you are prompted to select another scenario as the plan of record.
Manage Scenarios for a Roadmap
You can edit a roadmap item and its attributes in all scenarios but each change is specific to each scenario.
  1. Open a roadmap and click
    Scenarios
    .
  2. Click the
    Scenario
    drop-down and click
    MANAGE
    .
  3. Click the
    ⋮ Actions
    menu next to a scenario to manage the scenario as follows:
    • Rename the scenario
    • Delete the scenario
    • Set the scenario as the POR and remove the POR tag from any previous POR scenario.
    • Make the scenario the baseline and remove the baseline tag from any previous baseline scenario.
    • Remove the baseline tag from a baseline.
  4. Click
    X Close
    .
Select an OBS Unit for a Roadmap
As a portfolio manager, you can restrict and limit OBS associations on roadmap objects. Only users having OBS-level access rights or global roadmap rights can view the roadmap objects associated with their OBS. To associate roadmaps with an OBS unit, see in the
Classic PPM
Administration documentation. After you associate a roadmap with an OBS, you can select an OBS unit for the roadmap in
Clarity
.
Follow these steps
:
  1. Navigate to a roadmap. You must have an OBS unit or global roadmap access rights to view or edit the roadmap.
  2. Click the
    Details
    button.
    The associated OBS attribute for the roadmap appears.
  3. Select an OBS unit for the roadmap.
Create and Use Custom Attributes for Roadmaps
Sid - a Portfolio Manager creates roadmaps to build top-down plans and initiatives. He wants to attach a custom attribute called confidence level with the roadmap items. He can set the confidence level to high, low, or medium and use it to guide his investment decisions. Let’s see how the
Clarity
administrator helps Sid by first creating a lookup and then a custom attribute.

Follow these steps:
  1. Open
    Classic PPM
    and select
    Objects
    .
  2. In the Object Name field, type
    Roadmap Item
    and press Enter.
  3. Select the
    Roadmap Item
    object.
  4. Select the
    Attributes
    tab and click
    New
    to create a new attribute.
  5. Click
    Save and Return
    to finalize your changes.
Using Process with Roadmaps
The Roadmaps object has been enhanced to support processes in this release. You can now invoke processes based on creation or updates roadmaps. Customers can now use a process to push a roadmap item to another system, such as Rally, for execution.
  • Roadmaps are event enabled to allow processes to run against it.
  • The roadmap will appear as an option under the primary object for processes.
  • Processes can run when you create and update of roadmaps.
  • Roadmaps are automatically event enabled after upgrade. Customers have the option to “uncheck” the event-enabled flag.
  • Processes executed against a roadmap can only be seen in
    Classic PPM
    .
  • Processes built with action items still require you to act on it in
    Classic PPM
    .
  • Processes cannot be run on roadmap items. However, process start condition can use roadmap, roadmap items, or roadmap item dependency attributes.
  • If you change the name of a custom investment then the “Event Enabled” flag gets unchecked.
  • If you create an action item process then the notification link to the Roadmap does not work.
  • There is no option to start a process “On Demand” even if you select that option in the process definition. You can run these processes by using the “Execute a Process” job.
For more information on how you can leverage processes in
Clarity
, see Configure Processes.
Enabling Field-Level Security for Roadmaps and Roadmap Items
Linked
Roadmap and Roadmap Item attributes can be secured using field-level security (FLS).  You can use FLS to provide access to specific attributes or fields for specific user groups. Roadmap and Roadmap Item field-level security apply only to Clarity and not Classic PPM.
Some of the key points you need to remember are:
  1. The administrator grants and revokes field access at the group level.
  2. The following items cannot be secured by FLS:
    1. Roadmap - ID, Name, Start Period, Start, Finish, Blueprint Active ID
    2. Roadmap Item - ID, Name, Start, Finish, Currency*, In Plan*, Per-period metrics (e.g., TSV)*
  3. FLS always has precedence over defined Roadmap or Roadmap Item Object security access rights. 
  4. From a third-party integration perspective, the "Integration User” will have access to secured attributes.
{ URL:"/roadmaps", description:"Using roadmaps enable you to focus on business outcomes so that planning is visual, interactive and collaborative", admin: "You need relevant access rights to access this" troubleshooting:{ text: "the following KB articles will help you" URL:["https://techdocs.broadcom.com/us/en/ca-enterprise-software/business-management/clarity-project-and-portfolio-management-ppm-on-premise/16-0-0.html", "https://techdocs.broadcom.com/us/en/ca-enterprise-software/business-management/clarity-project-and-portfolio-management-ppm-on-premise/16-0-0/release-information.html"] } Pendo:"guideid", Video: ["FirstvideoURL","secondvideoURL"] }