Portfolio Performance Management practice questions

Remove the project manager from the project.

Why it fails: This is an escalation that should happen only after other steps fail.

Ignore the reporting issue as long as the project is successful.

Why it fails: Governance must be maintained for consistency.

Do the reporting for them.

Why it fails: The project manager is responsible for their own reporting.

Local weather reports.

Why it fails: Irrelevant.

Individual team member weekly timesheets.

Why it fails: Too granular for the portfolio level.

Personal email of the CEO.

Why it fails: Irrelevant.

Conduct a root cause analysis to determine why the program is not meeting market penetration KPIs.

Why it fails: This is incorrect because while root cause analysis is valuable, the portfolio manager's primary responsibility is to ensure portfolio alignment with strategy. The program may be executing well but on the wrong objectives. The first step should be to review strategic alignment, not to dive into operational root causes, which is more appropriate for the program manager.

Escalate the issue to the Portfolio Governance Board and recommend cancelling the program immediately.

Why it fails: This is incorrect because immediate cancellation is premature. The portfolio manager should first analyze the program's alignment and performance data to make an informed recommendation. Escalation without thorough analysis could lead to losing valuable investments and missing opportunities. The governance board expects a well-reasoned proposal based on portfolio performance management.

Instruct the program manager to focus on improving market penetration metrics by reallocating resources from other portfolio components.

Why it fails: This is incorrect because the portfolio manager should not unilaterally reallocate resources from other components without a strategic review. The issue may be that the program itself is not aligned with the portfolio strategy, and simply improving metrics might not address the root cause. The portfolio manager must first evaluate alignment before taking resource actions.

Request a revision of the organization's corporate strategy.

Why it fails: Revising corporate strategy addresses the wrong side of the misalignment: the framework exists to measure component outcomes against existing strategic objectives, so altering strategy discards the baseline rather than correcting measurement. It would be right only when the strategy itself is genuinely obsolete, not when tracking is faulty.

Increase the frequency of status reporting from project managers.

Why it fails: More frequent reporting increases the volume of the same misaligned metrics without changing what is measured or how outcomes map to objectives. Reporting cadence is a monitoring control, correct when stakeholders need earlier visibility of known-good data, not when the measurement definitions themselves are misaligned.

Change the KPI definitions to show better alignment.

Why it fails: Redefining KPIs to display better alignment manipulates the measurement rather than fixing the underlying outcome-to-objective linkage, masking the real gap. KPI redefinition is legitimate when metrics genuinely no longer reflect strategic intent, but here it fabricates alignment instead of achieving it.

Re-classify the project as a 'support activity'.

Why it fails: Re-classifying as a support activity relabels the project without addressing that its output is now irrelevant; support activities still consume funding and resources. The portfolio manager should re-evaluate the component and recommend termination or re-prioritisation. Re-classification suits genuinely ongoing operational work, not a project whose benefits have evaporated.

Ask the steering committee to change the portfolio strategy.

Why it fails: The portfolio manager owns portfolio-level optimisation within the agreed strategy; asking the steering committee to rewrite strategy misplaces the decision and delays action. The next step is to re-evaluate the project against current strategic objectives and recommend termination or re-scoping. Strategy change is the committee's call when the mandate itself is obsolete.

Continue the project to avoid wasting past investments.

Why it fails: Sunk costs are irrecoverable and must not drive continued investment; continuing consumes capacity that relevant initiatives need. The portfolio manager should re-evaluate the project against current strategic objectives and recommend termination. Continuation would be justified only where the output still delivers benefits aligned to the revised portfolio strategy.

Resource utilization rates per employee.

Why it fails: Per-employee utilisation is operational resourcing data, too granular for an executive steering committee that governs portfolio investment and benefit delivery. It would suit a resource manager balancing allocations, not executives needing aggregated portfolio-level performance against strategic objectives.

Individual task-level completion status.

Why it fails: Task-level completion status belongs to project scheduling, not portfolio reporting; executives need aggregated component and investment performance. It is tempting because task tracking is the operational mechanism project managers use daily, and it would be correct when reporting progress to a project team or sponsor, where schedule detail drives delivery decisions.

Detailed project risk registers.

Why it fails: Detailed risk registers are operational artefacts owned by project and programme managers; executives need aggregated risk exposure across the portfolio. Registers are correct for active risk mitigation work, not for steering-committee reporting on portfolio-level performance and strategic alignment.

Suspend the program until the end of the fiscal year.

Why it fails: Suspension halts delivery without removing the added scope, so costs resume unchanged and benefits slip. It is tempting as a circuit-breaker for runaway spending, which fits programmes needing investigation before further funding, not one whose scope must be re-baselined.

Approve the budget increase to prevent project failure.

Why it fails: Approving extra funds legitimises the scope creep rather than controlling it, so the portfolio absorbs unauthorised change. It is tempting because additional funding is legitimate when a formally approved change request with supporting business case justifies it.

Reduce the budgets of other programs to accommodate this one.

Why it fails: Robbing other programs does not address the scope creep causing the overspend; it merely redistributes the shortfall and damages unrelated benefits. It is tempting as portfolio-level rebalancing, which is valid when strategic priorities genuinely shift, not to fund uncontrolled scope.

Allocate resources to the project with the earlier deadline.

Why it fails: Prioritising by deadline ignores strategic alignment and capacity, so the conflict persists and the portfolio suffers. It is tempting because deadline-driven sequencing works for single-project scheduling, where delivery dates, not cross-portfolio optimisation, govern resource assignment.

Request additional budget to hire temporary contractors for both projects.

Why it fails: Hiring contractors adds cost and capacity without resolving the conflict over the same constrained pool, so both initiatives still contend for the identical scarce skill. It is tempting because it appears to protect both projects, yet it would be correct only where the constraint is budget rather than a limited specialist resource.

Require both project managers to negotiate a resolution independently.

Why it fails: Delegating to the project managers leaves the shared constraint unresolved, since neither owns the portfolio-level trade-off. It is tempting because negotiation suits peer-to-peer conflict within one programme, where both managers report to the same governance and can trade scope directly.

Terminate these components immediately.

Why it fails: Immediate termination discards a component delivering high ROI, forfeiting returns that could fund strategic initiatives. Termination suits components with both low strategic value and poor financial performance. Where returns remain strong, the portfolio should realign, restructure or phase the component rather than eliminate it outright.

Continue funding to capitalize on the high ROI.

Why it fails: Portfolio optimisation ranks components on strategic alignment, not financial return alone, so high ROI cannot justify retaining a component contributing nothing to strategic objectives. Continued funding suits components that advance strategy while meeting return thresholds. Low strategic value indicates realignment, reduction or exit rather than ongoing investment.

Transfer these components to a different portfolio.

Why it fails: Transferring to a different portfolio does not resolve low strategic alignment; the component still consumes investment without advancing the receiving portfolio's objectives. Transfer suits components misaligned with one portfolio but genuinely fitting another's strategy. High ROI with low strategic value calls for realignment, reduction or divestment instead.

Portfolio Strategic Plan

Why it fails: The Portfolio Strategic Plan defines strategic alignment, but value measurement definitions sit in the Portfolio Value Management Plan, which specifies metrics, thresholds and reporting. The Strategic Plan guides initiative selection and prioritisation. It would be the correct source when determining how the portfolio aligns with organisational strategy, not how value is quantified.

Portfolio Charter

Why it fails: The Portfolio Charter authorises the portfolio and defines its scope, governance and high-level objectives, but it does not specify value measurement methods. The Portfolio Strategic Plan holds that detail. A charter would be the right artefact when formally initiating and mandating a new portfolio, not when defining metrics for measuring value delivery.

Portfolio Roadmap

Why it fails: The Portfolio Roadmap is a time-based visual of initiatives, milestones and dependencies; it shows when components deliver, not how value is measured. Metrics, baselines and measurement methods belong in the Portfolio Value Management Plan. A roadmap would be the right artefact when communicating sequencing and scheduling of portfolio components to stakeholders.

Adjust the resource allocation for all active components.

Why it fails: Reallocating resources across all active components applies a remedy before the cause of the ROI shortfall is known, potentially worsening it. It is tempting because resource reallocation is a genuine portfolio management lever, but it belongs after analysis identifies which components underperform; the first step is investigating the variance itself.

Terminate underperforming components immediately.

Why it fails: Terminating components immediately acts on the symptom before identifying which components caused the shortfall, risking removal of healthy investments. It is tempting because portfolio managers do prune underperforming components, but that decision follows performance analysis and review; the first step is investigating the variance's causes, not executing terminations.

Update the Portfolio Strategic Plan to align with lower ROI expectations.

Why it fails: Rewriting the strategic plan to accept lower ROI legitimises the shortfall before any root-cause analysis, and the plan is an output of portfolio strategy, not a variance-response tool. It is tempting because strategic plans do get revised when forecasts shift, but that follows investigation; the manager must first analyse which components drove the variance.

Selecting new vendors.

Why it fails: Vendor selection belongs to portfolio resource management and procurement, not monitoring. Monitoring tracks existing component performance against strategic objectives through metrics, dashboards and reviews. Selecting vendors would be correct during portfolio construction or optimisation, when deciding how to resource initiatives.

Updating individual project charters.

Why it fails: Portfolio monitoring tracks aggregate performance, risk and resource allocation across the portfolio, not individual project charters, which are authorised at project level. Charter updates belong to project initiation or change control. Portfolio monitoring would be correct when assessing strategic alignment, balancing investment or reallocating resources across components.

Managing daily project tasks.

Why it fails: Daily project task management sits with project managers, not the portfolio monitoring process. Monitoring aggregates component-level performance data to assess alignment with strategic objectives and rebalance the portfolio. Managing daily tasks would be correct for a project manager executing an approved project schedule.

The Project Charter.

Why it fails: The project charter authorises the project's initiation and is not revised to reflect its closure; it remains a historical authorisation artefact. The portfolio management plan and portfolio register capture closure outcomes and status updates. A charter is the correct document when formally authorising a new project, not when recording its completion.

The Corporate Strategic Plan.

Why it fails: The Corporate Strategic Plan sets long-term organisational direction and is revised on strategic cycles, not at individual project closure. It is tempting because portfolio components must align to strategy, and strategic shifts can trigger portfolio rebalancing. However, closing a project updates the portfolio register or component inventory, not the strategic plan itself.

The Human Resources handbook.

Why it fails: The HR handbook governs organisation-wide employment policy, not portfolio artefacts, so project closure never triggers its revision. It is tempting because closure does involve releasing staff and updating personnel records, and the handbook would legitimately be revised when employment terms, benefits or leave policies change — a governance activity unrelated to closing a single project.

Elimination of all high-risk projects.

Why it fails: Balancing deliberately retains some higher-risk, higher-return initiatives to meet strategic objectives; removing every high-risk project skews the portfolio toward low-yield work. Elimination is tempting because it appears to reduce exposure, and would be correct if the organisation's risk appetite prohibited all high-risk investment.

All projects have the same budget and timeline.

Why it fails: Balancing varies investment levels, durations and priorities across components to optimise value; equalising budgets and timelines ignores each initiative's distinct contribution. Uniformity is tempting because it looks fair and simplifies planning, and would be correct where components are genuinely equivalent in scope, risk and expected return.

Uniform resource utilization across all departments.

Why it fails: Balancing seeks an intentional mix of risk, return, timing and strategic alignment; identical utilisation across every department is neither achievable nor desirable. Uniform utilisation is tempting because it appears equitable and avoids resourcing conflicts, and would be correct only if the portfolio's goal were operational load-levelling rather than value maximisation.

Vendor contract expiration dates.

Why it fails: Contract expiry dates are an operational scheduling input, not a driver of what-if scenario modelling, which tests portfolio outcomes against changed strategic assumptions such as funding cuts or benefit shifts. Expiry tracking belongs in procurement or vendor-management reviews, where renewal timing and commercial leverage are the actual concerns.

Project manager availability.

Why it fails: What-if analysis weighs scenarios by strategic alignment, value and risk; individual project manager availability is a resourcing detail, not the primary factor. It is tempting because capacity constrains portfolios, and would be correct when modelling resource-constrained scenarios, not as the primary consideration.

Team morale.

Why it fails: What-if analysis compares scenarios against strategic objectives, cost, risk and benefit; team morale is not the primary axis. It is tempting because morale affects delivery capacity, and would be correct as a secondary constraint when assessing resource-driven scenarios, not as the primary consideration.

Hire more staff for every project.

Why it fails: Hiring for every project ignores portfolio-level capacity balancing, which requires prioritising and reallocating existing resources across competing initiatives. It is tempting because adding headcount genuinely resolves a single project's shortfall, and would be valid where one project alone is under-resourced and budget permits.

Remove the resource constraints from the portfolio plan.

Why it fails: Deleting resource constraints from the portfolio plan removes the visibility of the bottleneck without creating capacity, leaving demand still exceeding supply. It is tempting because it makes the plan appear feasible on paper, but portfolio capacity management requires balancing demand against real supply through prioritisation and levelling, not erasing the constraint.

Ask all project managers to work overtime.

Why it fails: Overtime adds finite extra hours without resolving the underlying capacity shortfall, and sustained overtime degrades throughput and quality. It is tempting because it appears to expand capacity quickly without reprioritising work, but portfolio bottleneck management requires demand shaping, prioritisation and resource levelling rather than pushing existing staff harder.

Approve it because the NPV is high.

Why it fails: High NPV alone bypasses portfolio-level evaluation; the manager must assess how the risk-profile shift affects aggregate portfolio risk, correlation and balance before approving. NPV-only approval fits projects within existing risk tolerances, where no portfolio-level rebalancing or governance review is triggered.

Submit the proposal to the project managers for their input.

Why it fails: Deferring to project managers inverts governance: portfolio decisions rest with the portfolio manager, who owns risk-balance trade-offs across the portfolio. Seeking project-manager input suits execution planning or resourcing feasibility, not approving a proposal that alters the portfolio's risk profile.

Reject it because it changes the risk profile.

Why it fails: Rejecting outright ignores portfolio governance: the manager should weigh the risk-profile change against strategic alignment and rebalancing, not veto on risk alone. Rejection suits proposals breaching risk tolerance or regulatory limits, where no mitigation can bring exposure back within appetite.

Create a new Portfolio Management Plan.

Why it fails: Creating a new Portfolio Management Plan addresses governance documentation, not the variance itself; the plan defines structure, components and strategic alignment, and is authored during portfolio initiation or realignment. Variance analysis instead feeds corrective action through the portfolio's governing body, such as rebalancing components or revising the strategic plan.

Inform the project managers that they are failing.

Why it fails: Informing project managers of failure addresses individuals rather than the portfolio's governance process. Variance analysis exists to trigger replanning, rebalancing or stage-gate decisions at portfolio level, not performance notification. It would be tempting where a single project's delivery is underperforming and line-management escalation is genuinely warranted.

Immediately cut the budget of all low-performing projects.

Why it fails: Cutting budgets addresses symptoms rather than the portfolio governance process the stem requires: variance analysis feeds a portfolio review, where the manager rebalances components, adjusts the strategic plan, or recommends termination through formal decision-making. Budget cuts are tempting as cost-control, and would fit a project-level corrective action once a specific component's funding is genuinely the root cause.

Individual team member feedback.

Why it fails: Individual team member feedback addresses operational performance, not the portfolio-level investment mix, benefit realisation, and strategic alignment stakeholders need monthly. It is tempting because feedback informs resource management and team development, and would suit a project or programme status review, yet PfMP reporting prioritises aggregated portfolio value, risk exposure, and progress against strategic objectives.

Daily task completion percentages.

Why it fails: Daily task completion percentages are too granular for a monthly portfolio report and do not reflect strategic portfolio value. They would be appropriate in a team-level status meeting or daily stand-up, where tactical progress is tracked.

Vendor contract details.

Why it fails: Vendor contract details serve procurement and contract management, not portfolio-level stakeholder reporting. A monthly portfolio report prioritises aggregate performance: benefits realisation, investment status, and strategic alignment across components. Contract specifics would be relevant when managing an individual vendor relationship or resolving a procurement dispute, not when communicating portfolio progress to stakeholders.

Project team conflicts.

Why it fails: Project team conflicts arise inside the performing organisation, so they are an internal influence on portfolio performance. External influences originate outside the organisation's control, such as regulatory changes, market shifts or supplier failures, which is when this classification would be correct.

Portfolio budget cuts.

Why it fails: Portfolio budget cuts are decided internally by executive governance, making them an internal influence. External influences come from outside the organisation's control, such as regulatory changes, economic shifts or competitor actions, which is the scenario where this option would be correct.

Internal resource turnover.

Why it fails: Internal resource turnover occurs within the organisation's own staffing and is therefore an internal influence on portfolio performance. External influences originate beyond organisational control, such as regulatory change, market volatility or supplier failure, which is when this classification would be correct.