Planview Portfolios
Key Info:
Planview Portfolios is an enterprise project and portfolio management product for connecting strategy, investments, resources, programmes, projects and financial plans.
Details
Portfolio management scope
Planview Portfolios is an enterprise project and portfolio management product that connects strategic objectives, investments, programmes, projects, resources and financial plans. Its official product scope includes prioritisation, roadmaps, capacity planning, scenario comparison and portfolio reporting. It is aimed at cross-project governance and strategic execution rather than being only a team task tracker.
Evaluation scenario
Create a sample portfolio containing proposed and active initiatives with benefits, costs, resource demand, milestones and dependencies. Rank the proposals against agreed drivers, compare at least two funding and capacity scenarios, then approve one plan. Introduce a budget reduction and a scarce-role constraint to test whether decision makers can see consequences before changing commitments.
Strategy and prioritisation
Map objectives, outcomes and investment criteria before configuring scoring. Test whether executives can trace a funded initiative to the strategy it supports and whether teams can explain why lower-ranked work was deferred. Weighted scores should inform a decision without hiding assumptions, so evaluators should inspect formulas, overrides and the evidence behind each rating.
Capacity and financial planning
Model people, skills, costs and target budgets at the level used by the organisation. Compare demand with available capacity across programmes and time periods. Test part-time assignments, shared specialists, delayed hiring and changes between capital and operating expense. Reconcile portfolio totals with the finance and resource systems that remain authoritative.
Execution and dependencies
Assess how programme milestones, projects, agile work and dependencies roll into portfolio views. Trial one delayed project and one cross-portfolio dependency, then observe forecasts, alerts and executive reporting. Teams should not have to duplicate detailed delivery data simply to produce a portfolio status, so integration and ownership boundaries need explicit testing.
Governance and reporting
Review roles, approval workflows, audit evidence, dashboards and scenario permissions. Build separate views for executives, portfolio managers, finance and resource owners. Test a decision reversal and reproduce who changed funding, priority or dates. Reporting should expose assumptions and stale data rather than presenting a precise but unsupported portfolio picture.
Rollout and adoption
Start with one portfolio and a small decision forum whose current planning cadence is documented. Measure time spent assembling reports, unresolved data issues, late resource conflicts and decision turnaround. Define owners for strategy, demand, finance, capacity and delivery feeds. Expand after the pilot can repeat a full prioritisation cycle without shadow spreadsheets becoming the real system of record.
Decision checkpoint
Proceed when leaders can compare investments transparently, planners can reconcile capacity and finance, teams can trace dependencies, and governance produces an auditable decision history. Hold rollout if scoring obscures judgement, data ownership remains unclear or portfolio reports depend on manual updates that cannot be reproduced.