Skip to main content

 

Language Selector

  1. Other Languages

    (machine translation)

Planview Customer Success Center

Roadmapping

  1. Last updated
  2. Save as PDF

Roadmapping

The Roadmapping capability supports the translation of strategy into a timeline of business outcomes and deliverables. Each capability within the Planview Capability Framework has a distinct set of features and functionality, business processes, best practices, and analytics and reports that deliver value to customers in the form of specific business outcomes.

Definition and Business Outcomes

Definition

Roadmaps allows business leaders, product and program managers, and others to translate strategy into a timeline of business outcomes and deliverables. These roadmaps can be used to set direction and expectations, as well as maintain clear communication throughout delivery.

Business Outcome

We can translate strategic ideas into a tangible timeline of business outcomes and deliverables.

Business Outcome

We can set direction for scheduling and define key milestones in order to meet expectations.

Best Practices

Ensure the right people have access

Ensure that all stakeholders involved in the roadmap deliverables/outcomes have access to your roadmap so they can view up-to-date changes and align across all levels of the organization. This will help you break down silos during the planning process and bring together the right expertise across business units, teams, and geographies.

Review your roadmap regularly

Review your roadmap on an ongoing basis, such as quarterly, and maintain an adaptive and responsive mindset as you learn new information about the product/market or receive customer feedback. Reassess, adapt, and communicate changes to stakeholders as your roadmap evolves—but to maintain stakeholder confidence in your strategic decision-making process, avoid continuously updating or never updating your roadmap.

Tailor the level of detail

Tailor the level of detail on your roadmap to your audience. For example, a portfolio roadmap for executives may have a monthly or quarterly planning horizon that covers multiple products with very few detailed activities, whereas a development roadmap may include just one product over a shorter, two-week planning sprint, broken down into detailed development stories and tasks. To gain stakeholder buy-in, your roadmap should have just enough detail to communicate the strategic vision, but not so much that it overwhelms viewers.

Use your roadmap as a collaboration tool

Collaboration is at the heart of every successful roadmap. Engage with stakeholders throughout the entire process. Not only does this keep them in the loop so they have a better idea of needs and expectations, it ensures that everyone’s priorities are aligned and that all executives and department heads are working together to achieve the same strategic business goals.

Evolve your IT roadmap

Develop a flexible and up-to-date IT roadmap that doesn’t just focus on tech outcomes—this ensures that technology is factored into the decision-making process when executives are implementing or updating their business strategy. Increased collaboration between IT leaders and executives breaks down silos that cause work-related problems—such as new software projects failing or lack of stakeholder involvement in tech-related projects— and ensures both departments are working together to achieve the same outcomes.

Baseline your roadmap

Once you’ve finalized your plan, baseline your roadmap for future reference and tracking. As you execute the plan and your roadmap evolves based on changes in the competitive landscape or customer feedback, compare your actual plan to the baseline to measure progress against/adherence to the baseline and identify variances.

Processes and Reports

conceptual image_roadmapping.jpg

Roadmaps allows business leaders, product and program managers, and others to translate strategy into a timeline of business outcomes and deliverables​. Roadmaps can be used to set direction and expectations, illustrate dependencies, track the status of deliverables, and maintain clear communication throughout delivery.

Select your product

           

Roadmapping Process Steps

           

E1 Process Roadmapping.png

Roadmapping process flow

           

Process Step Description

Create program

The purpose of this step is to create new strategic programs. To add a new program at the lowest level of the strategy structure, click the +New option in the top right or click the +New Program option on the action menu from its parent level.

See Creating a Strategic Entity for more information

Create outcome/product

Outcomes are the deliverables of your investments (such as, projects and programs).   These deliverables are typically products, applications, and services.

The purpose of this step is to create new a new outcome/product.

See Creating an Outcome for more information

Plan roadmap dates and milestones

The purpose of this step is to define the target dates and milestones of the program. This allows the program manager to align the program schedule and the schedule of the associated entities that will deliver the program.

Baseline roadmap

Roadmap baselines are snapshots of the strategy or outcome roadmap, including target dates and actual/schedule dates of associated entities. 

The purpose of this step is to capture a baseline of the strategy or outcome which represents a record of the roadmap dates and associated entities as of this time. 

See Outcome Baselines and Strategy Baselines for more information on capturing baselines

                      

           

Roadmapping Process Steps

AdaptiveWork Roadmaps exist on Project, Programs, and Portfolios, and provide managers and executives with an interactive visualization tool to review and assess their strategies. The Portfolio roadmap can group related projects by a selected criteria— such as product name—for the review and approval process.

           

CZ Process Roadmapping.png

Roadmapping process flow

           

Process Step Description
Create the project

Create the project(s).
Create the program  Create the program(s).
Create the portfolio

Create the portfolio(s).
Create the Roadmap

Create the roadmap from the Roadmap panel for projects, programs, or portfolios. Enter in the name and grouping, if desired.

           

Click to expand or shrink

Create the Roadmap

           

           

Click to expand or shrink

View Roadmaps

           

For more information, see the following articles:
Add key milestones and key dates

For projects and programs, interact with the roadmap to see project or program information by hovering over a project or clicking on a project bar, add key dates, and adjust settings as needed. The roadmap may be filtered to only show the level of information needed, manually scaled, and cross-project dependencies may also be displayed to help provide the full picture. 

           

Click to expand or shrink

Example of Roadmap by Investment Type

           

For portfolios, add key milestones, key dates, and adjust settings as needed. As projects are added or removed from the portfolio, the roadmap will be updated automatically. It can also be manually refreshed using the refresh action in the three-dot menu. 

           

Click to expand or shrink

Add Milestones

      

                      

Related Capabilities

Supported Solutions