Scenario planning software for project portfolios lets a PMO copy the current plan, change one thing (the budget, a start date, a hire) and see what happens to the funded list, the capacity load by role and the benefit dates before anyone commits. The useful tools keep several scenarios side by side and compare them on the same scorecard. For most PMOs the choice is between an enterprise PPM suite with what-if planning built in, a capacity-first portfolio tool, or a focused scoring and capacity workspace on top of the tools teams already use.

Key takeaways

  • A portfolio scenario changes funding, timing or capacity and shows the effect on all three at once. Budget-only scenarios miss the people problem.
  • Cutting the budget can make capacity worse, because the projects that drop out are not always the ones using your scarcest role.
  • Delaying one large project is often the cheapest scenario, and only a role-level plan shows it.
  • In a demo, ask the vendor to build three scenarios from your data and compare them on one screen.

What portfolio scenario planning has to do

Finance teams have used scenario models for years, usually for revenue and cost. Portfolio scenarios are different because the constraint that bites first is rarely money. It is a handful of roles that every project needs at the same time: data engineers, integration developers, solution architects, a validation team in life sciences. So a tool that only re-adds project budgets under a lower ceiling answers half the question.

A scenario worth presenting to a steering committee shows four things together. Which projects are funded and which fall below the line. The in-year cost against the ceiling. Demand against capacity for each scarce role, month by month. And the dates when the main benefits now arrive. If the software cannot show all four for two scenarios side by side, the PMO ends up rebuilding the comparison in slides, which is the work the tool was bought to remove.

A worked example with three scenarios

A PMO has nine candidate projects for next year, a budget ceiling of $12.0M and one scarce role: six data engineers. At 85 percent availability that is 6 x 12 x 0.85, about 61 person-months of data engineering. Projects are already scored on the PMO's weighted model.

ProjectScoreIn-year costData engineer person-months
P1 Customer portal rebuild82$2.4M14
P2 ERP upgrade78$3.1M10
P3 Data platform75$1.8M18
P4 Pricing engine70$1.2M9
P5 Mobile app refresh64$0.9M4
P6 Warehouse automation61$2.2M6
P7 Compliance reporting58$0.8M7
P8 CRM consolidation52$1.5M8
P9 Analytics self-service47$0.7M6

Swipe to see more →

Funding strictly by score until the money runs out gives three very different answers depending on the assumption you change.

ScenarioProjects fundedIn-year costData engineer demandLoad on 61 person-months
A. Baseline, $12.0M ceilingP1 to P6$11.6M61100%
B. Budget cut 15 percent, $10.2M ceilingP1 to P5 and P7$10.2M62102%
C. $12.0M ceiling, P3 starts in Q3P1 to P7$11.5M5997%

Swipe to see more →

Scenario A looks fine on money and has zero slack on data engineers, so the first sick week or late requirement slips something. Scenario B is the surprise. Spending $1.4M less drops warehouse automation, which uses few data engineers, and lets compliance reporting in, which uses more. The portfolio is cheaper and more overloaded. Scenario C delays the data platform by six months, which halves its in-year cost to $0.9M and its data engineer demand to 9 person-months. Seven projects fit, the load falls to 97 percent, and the price is a later date for the data platform's benefits.

None of this is hard arithmetic. It is hard to keep straight across nine projects, monthly demand and a steering meeting where someone asks "what if we also delay P2". That is the job of scenario planning software: hold the copies, recalculate the role load and show the comparison without a rebuild.

Which scenario planning tools work for project portfolios?

Four categories show up on PMO shortlists. Enterprise PPM suites, capacity-first portfolio tools, finance planning platforms and spreadsheets. They differ less in whether they can model a scenario than in what they treat as the constraint.

CategoryExamplesWhat a scenario changesBest forWatch out for
Enterprise PPM suitesPlanview, Planisware, Broadcom ClarityFunding, timing and resources in one modelLarge PMOs where finance and resource data already live in the suiteQuoted pricing and a long setup before the first scenario. See Planview vs Planisware
Capacity-first portfolio toolsMeisterplan, Tempus Resource, KiplotStart dates and resource assignments, dragged on a timelinePMOs whose main fight is over shared peopleBenefits and scoring are thinner than the capacity view
Finance planning platformsAnaplan, Workday Adaptive PlanningBudget lines and driversFinance-led portfolios measured on spendNo role-level demand from projects unless you build it
SpreadsheetsExcel, Google SheetsWhatever you copy and editFewer than 20 projects and one analyst who owns the modelVersion drift, and nobody else can rerun the scenario in the meeting

Swipe to see more →

There is a fifth option that sits between spreadsheets and suites: a focused workspace that holds the scored initiative list, the funding line and the capacity plan by role, so a scenario is a change to the ceiling or a start month and the ranking and load update together. Our project prioritization tool handles the scoring and funding line, and the capacity planning tool shows demand against capacity by role, month by month. Neither replaces a delivery tool or timesheets.

If your scenarios are mostly about a single program rather than the whole portfolio, the comparison of program management software covers tools that hold dependencies and benefits across a program.

How much does scenario planning software cost?

Price follows the category. Enterprise PPM suites quote per user per year, usually with implementation services, and scenario planning is part of the portfolio module rather than an add-on. Capacity-first tools also quote, often by number of planners and viewers. Finance platforms are licensed to finance users. Our breakdown of PPM software pricing shows what drives each quote, and the Planview pricing and Celoxis pricing pages go vendor by vendor.

Scenario work also depends on cost data that arrives from outside the portfolio tool. When project expenses are approved in a separate tool, keep the in-year actuals feed simple. Teams that already use expense software with budget limits per project can export actuals by project each month and load them as the starting point of the next scenario.

Can you do portfolio scenario planning in Excel?

Yes, for a small portfolio with one owner. Keep one tab per scenario with the same columns (project, score, in-year cost, demand by role by month) and a summary tab that compares them. It breaks when a second person edits a copy, when monthly role demand pushes the sheet past a few thousand cells, or when the steering committee wants a new scenario during the meeting. That is usually the moment to buy.

Who should own scenarios in the PMO?

The portfolio manager or PMO analyst who owns the scoring model should build scenarios, and finance should agree the ceiling and the cost basis before the first one is shown. The Project Management Institute's Standard for Portfolio Management treats this as part of portfolio optimization: comparing component mixes against strategy and constraints before authorizing them. Scenarios that come from the project managers themselves tend to protect their own projects.

Five tests for any scenario planning demo

  1. Use your own projects. Load at least ten real candidates with cost and role estimates, not the sample portfolio.
  2. Change the ceiling. Cut the budget by 15 percent and check that the funded list and the role load both update.
  3. Move a start date. Delay one large project by two quarters and see whether in-year cost and monthly demand shift with it.
  4. Compare three side by side. Ask for baseline, cut and delay on one screen with the same columns.
  5. Export the result. The comparison should leave the tool in Excel or CSV for the steering pack without a rebuild.

Scenarios only help if the inputs are honest. Our guides to resource capacity planning for portfolios and capacity planning software cover how to estimate role demand that holds up in the meeting.

E
Elena Marsh
PMO lead and portfolio strategist. Fifteen years building project management offices and running portfolio governance for technology and professional-services teams.