methodEnglish

Scenarios and protected choices

Compare explicit baselines and constraints without letting the solver erase real commitments or invent future capacity.

EnglishEspaƱolFranƧais

Documentation follows the current system language. Missing translations fall back to the page's canonical language.

Scenarios and protected choices

A scenario is a named set of editable conditions: manual or optimization mode, scoring weights, protected and locked-out initiatives, capacity multipliers, and justified resource-period overrides. Keep the baseline intact and explain why each scenario differs. Scenarios are comparisons, not forecasts and not separate versions of the approved plan.

Use manual mode to evaluate a set chosen by people; the engine checks it but does not optimize it. Use optimization mode to search the eligible set under encoded rules. Protected initiatives must remain selected and locked-out initiatives unavailable. Mandatory or committed work remains binding unless an authorized model edit changes its status; the assistant cannot infer or remove commitments.

Create a small set of decision-relevant cases: approved capacity, constrained capacity, and a defensible alternative policy may be enough. Avoid dozens of cosmetic scenarios. If a scenario changes capacity, score weights, or eligibility, record its provenance and review its downstream consequences.

Next: optimization, feasibility, and solver quality.

References

PMI — The Standard for Portfolio Management, Fourth Edition

Portfolio-management guidance connecting strategy, component selection, resource supply and demand, value, and governance.

https://www.pmi.org/standards/for-portfolio-management