Skip to main content

 

Planview Customer Success Center

Product Portfolio and Pipeline Planning

Product Portfolio and Pipeline Planning

The Product Portfolio and Pipeline Planning capability’s enablers include Business Requests, Intake, and Gated Process Automation (Stage-Gate). 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.

Processes and Reports

conceptual image_product portfolio and pipeline planning.jpg

Product portfolio and pipeline planning supports a clearly defined process to initiate business requests and collect relevant categorization and scoring information and initial financial data for business requests, projects, and programs that are initiated. A consistent intake process is created for new investments by ensuring the appropriate gated process is applied to projects, programs, and products, enabling accurate review and approval actions on these requests at each decision stage.

           

Business Requests Process Steps

           

Product Portfolio and Pipeline_ Business Requests Process Flow.jpg

Business requests process flow

           

Process Step Description
Create new request

Create new request entities, i.e., ideas for potential work that are entered into Planview Portfolios.  ​


For more information:

Describe and categorize request

During the initiation of a request, information is populated to describe and categorize the request. Often a minimum level of required categorization or descriptive information is enforced during the request creation lifecycle based on the information needs of the organization. ​

For more information:

Review and approve

Once you have a request portfolio, you can see detailed information regarding the requests that are included in your portfolio on the Portfolio Manager tile within the Request Portfolio View screen. This will allow the request to be reviewed in preparation for dispatch.

For more information:

Dispatch/associate request to project, program, or outcome/product

The purpose of this step is to connect the request with a relevant entity in Planview Portfolios. This can be achieved by either dispatching the request which generates a new entity or associating it with an already existing one.

Planview Portfolios can route requests to a dispatcher, who is the user responsible for evaluating the requests and then performing the following tasks. Depending on whether your system supports request lifecycles, a dispatcher can perform those tasks through request lifecycles or from the Request View screen without the use of lifecycles.

The dispatcher can:

  • Generate a new strategy, work (project), support ticket, product, or other outcome from a request.
  • Associate work, strategies, products, or other outcomes with a request.
  • Respond otherwise (such as rejecting the request) by changing the status of the request.
  • A dispatcher can share dispatching responsibilities with other users.

For more information:

Close request

If approval is not granted or the request is no longer needed, change the status to closed. This provides a record of its status for reporting and ensures that no further updates can be made to the request.

Depending on the internal business process, the process to close the request can vary and may contain approval gates in a lifecycle workflow. In these instances, successful completion of the lifecycle steps by the relevant users will automatically close the Request.

The status of the request can be changed in the Request Detail screen, or directly in the Portfolio Manager using an appropriate column set selection.

For more information:

                           

           

Intake Process Steps

           

Product Portfolio and Pipeline _Intake Process Flows.jpg

Intake process flow

           

Process Step Description
Create project/program

Create a record of the new project or program entity in Planview Portfolios. ​

For more information:

Describe and categorize project/program    

Creating a new project or program will include the creation of configuration-specific description and categorization attributes as determined by the organization's data and information needs. Capture the relevant descriptive and categorization information for the project or program. ​

For more information:

Plan initial project/program dates and milestones    

Build out the high-level schedule, with dates and milestones, for either the project or program. ​

For more information:

Forecast initial project/program financials

Capture a high-level estimate of the costs and benefits to deliver the project or program in the financial planning detail screen.

Based on the need of the organization, cost accounts can include labor, capital spending, and expense spending.​

For more information:

Review and approve

The project or program is taken forward for review and approval. ​

For more information:

             

           

Gated Process Automation Process Steps

           

Product Portfolio and Pipeline _Stage Gate Process Flow.jpg

Gated process automation process flow

           

 

Process Step Description
Update/record status of deliverables Prior to going through a gate, project or program managers should ensure that the status of all relevant deliverables are updated.
Complete gate assessment Project/program managers complete the gate assessment form – this is often in the form of a configured screen and includes the population of checklist items and fields related to the specific gate.
Submit for gate approval The project or program manager submits the gate assessment for approval.
Gate This step represents the gate decision point. Gate approvers review the gate assessment and status information then decide on whether to proceed with the project/program. ​
Record gate decision (approve) If the gate request is approved, the decision is recorded and the project or program proceeds to the next stage. ​
Record gate decision (reject) If the gate request is rejected, the decision and reason is recorded, then the project/program returns to the original gate for update/resubmission or moves into the closure process.
Close project/program

Change the project or program status to completed.

For more information: