5.4: PfMP style questions

Sample Questions

1. A multi-year digital transformation program has reached technical completion two weeks ahead of schedule and 5% under its approved budget ceiling. The project manager has closed out all vendor contracts and handed over administrative control of the platform to IT operations. Six months later, the quarterly portfolio review reveals that projected operating expense reductions are tracking 70% below baseline expectations. What is the most likely root cause of this portfolio performance failure?
   1. The portfolio manager failed to enforce rigorous CPI and SPI tracking during the project's execution phase.
   2. The organization failed to establish formal ownership with an operational Benefit Owner accountable on their operating P&L for post-handover process adoption.
   3. The portfolio governance board released the final funding tranche before the program manager completed post-implementation warranty support.
   4. The project manager did not include a positive schedule variance contingency buffer in the transition charter.
2. During a quarterly portfolio health evaluation, an executive director points out that a high-priority enterprise payments initiative reports an SPI of 1.15 and a CPI of 1.12, indicating that it is both ahead of schedule and operating under budget. However, the portfolio manager notes that customer complaint volume has surged by 45% during user acceptance testing, and early merchant pilot churn is at an all-time high. Which metric design principle should the portfolio manager invoke to address this systemic distortion with the governance board?
   1. Deploying earned schedule calculations to convert traditional schedule variance into time-based units.
   2. Establishing counterbalancing metric pairs to mitigate proxy gaming and the effects of Goodhart's Law.
   3. Expanding the portfolio management reserve to absorb post-launch operational warranty costs.
   4. Re-estimating the component's Budget at Completion using bottom-up parametric equations.
3. An enterprise Portfolio Management Office oversees 42 concurrent programs spanning four strategic themes. The executive steering committee complains that quarterly board meetings consistently devolve into granular debates over minor contractor travel variances while systemic delivery bottlenecks are overlooked. To reorient executive governance around high-leverage risk drivers, which analytical artifact should the portfolio manager present to the committee?
   1. A multi-tab tabular general ledger export showing 30-day trailing accounting transactions.
   2. A Tornado Diagram illustrating the sensitivity of net portfolio value across uncertain technical, regulatory, and market variables.
   3. Individual component Work Breakdown Structures highlighting task-level critical path dependencies.
   4. A cumulative team-level sprint burndown chart aggregating weekly story point velocity.
4. An in-flight strategic program has an approved BAC of $12,000,000. At the Month 9 stage-gate review, the PMIS reports PV = $7,500,000, EV = $6,000,000, and AC = $8,000,000. The enterprise portfolio governance framework defines Level 3 (Red) variance as any component with a CPI below 0.80 or an SPI below 0.85. What is the current performance posture of the program, and what mandatory governance action must be executed?
   1. CPI = 0.75, SPI = 0.80; the program is in Level 3 variance, requiring an automatic freeze on upcoming funding tranches pending an extraordinary steering committee review.
   2. CPI = 0.80, SPI = 0.80; the program is in Level 2 variance, requiring an exception memo and release of contingency reserves.
   3. CPI = 0.75, SPI = 0.89; the program is in Level 3 variance, requiring the immediate termination of the program manager.
   4. CPI = 1.33, SPI = 1.25; the program is operating well ahead of baseline, requiring no governance escalation.
5. A portfolio steering committee evaluates an initiative seeking capital authorization to replace a legacy enterprise core banking system. The business case documents significant gross financial benefits from automation and reduced licensing overhead. However, the portfolio risk officer points out that during the 12-month transition, call center inquiry wait times will temporarily double, and transaction processing latency will temporarily increase by 20%. How should the portfolio manager ensure these operational impacts are treated within the Benefits Register?
   1. Exclude the impacts from the business case, as temporary operational disruptions are project-level issues rather than portfolio governance matters.
   2. Classify the impacts as project scope defects and mandate that the engineering vendor absorb the associated costs under liquidated damages.
   3. Formally log the impacts as quantified disbenefits and deduct their economic friction from gross projected gains to determine net strategic portfolio yield.
   4. Rebaseline the corporate strategy to adjust customer service level agreements downward permanently.
6. An enterprise portfolio includes both deterministic, infrastructure-replacement programs and highly exploratory, AI-driven customer personalization features. The delivery teams for the AI features complain that traditional EVM metrics (SV and SPI) are producing misleading indicators because their scope backlogs are refined and reprioritized iteratively based on weekly user experiments. What should the portfolio manager do to maintain objective governance visibility across these adaptive components?
   1. Force the AI teams to lock a detailed 18-month Work Breakdown Structure and baseline all user stories before writing code.
   2. Exempt the AI components from all formal performance tracking and rely exclusively on quarterly verbal executive summaries.
   3. Supplement traditional EVM with Flow Telemetry metrics, measuring throughput, cycle time distributions, and flow efficiency across delivery queues.
   4. Replace the program managers with certified traditional scheduling professionals to enforce strict critical-path baseline control.
7. Following an unexpected regulatory audit, a global logistics firm is fined $18,000,000 when regulators discover that safety checks on automated sorting hubs were altered without authorization during a rapid expansion initiative. The investigation reveals that the decision to bypass the safety check was agreed upon verbally in an informal meeting to avoid missing a quarterly market launch milestone. Which portfolio governance practice was omitted, and what artifact should have been maintained to prevent this compliance failure?
   1. Parametric estimation; the portfolio office should have used historical analogous cost models.
   2. Decision provenance; the governance board should have maintained an immutable Enterprise Portfolio Decision Log recording the rationale, risk trade-offs, and voting authority.
   3. Rolling-wave cadence; the program team should have synchronized deployments using two-week sprint intervals.
   4. Resource smoothing; the portfolio manager should have reallocated certified safety inspectors from non-critical tasks.
8. A portfolio's PMIS aggregates data from twelve disconnected spreadsheets maintained independently by each program office. The executive dashboard frequently shows figures that contradict the underlying component reports by the time it reaches the steering committee. What is the most effective long-term fix?
   1. Ask each program office to submit their spreadsheets one day earlier each month.
   2. Consolidate reporting into a single integrated PMIS with a common data model, so figures are calculated once and shared consistently across governance levels.
   3. Have the portfolio manager manually reconcile discrepancies before every steering committee meeting.
   4. Reduce the reporting frequency to quarterly so fewer reconciliation errors occur.
9. A portfolio dashboard uses only red-yellow-green status indicators for all 42 components, with no supporting trend data. A newly appointed board member asks why a component has been "yellow" for six consecutive quarters without visible improvement or escalation. What does this reveal about the portfolio's graphical analytics approach?
   1. Status indicators alone are insufficient; the dashboard should also show trend lines and variance history so stagnation is visible, not just current state.
   2. Yellow status is acceptable indefinitely as long as the component has not turned red.
   3. The board member should not question status colors, since they reflect the program manager's judgment.
   4. Six consecutive quarters of yellow status is normal and requires no further analysis.
10. At portfolio closure, a component's original business case, risk register, and governance decision log are deleted to save storage costs, since the component delivered successfully. Two years later, a similar component is proposed, and the team has no record of the risks or trade-offs faced previously. What practice was violated?
    1. Artifact archival, which requires preserving key decision-making records to support future decision auditing and organizational learning.
    2. Resource smoothing, since resources were not reallocated efficiently at closure.
    3. Rolling-wave planning, since the component's plan was not elaborated progressively.
    4. MECE structuring, since the component overlapped with other portfolio elements.

Answer Key

1. B. Realizing operational outcomes requires a permanent Benefit Owner with P&L accountability, since project managers' responsibility ends at delivery.
2. B. Counterbalancing metric pairs guard against Goodhart's Law, where optimizing for cost and schedule alone can mask quality and experience damage.
3. B. A Tornado Diagram ranks uncertain variables by their potential swing on outcomes, redirecting governance attention to systemic risk over trivial detail.
4. A. CPI = EV/AC = 0.75 and SPI = EV/PV = 0.80, both breaching the Level 3 thresholds and triggering an automatic funding freeze and extraordinary review.
5. C. Disbenefits are measurable negative outcomes that must be logged and deducted from gross gains to determine true net portfolio yield.
6. C. Flow Telemetry (throughput, cycle time, flow efficiency) preserves governance visibility for adaptive work where the scope baseline is not static.
7. B. An immutable Enterprise Portfolio Decision Log records the rationale and trade-offs behind strategic decisions, supporting regulatory and fiduciary oversight.
8. B. A single integrated PMIS with a common data model prevents figures from diverging across disconnected spreadsheets and reporting levels.
9. A. Trend lines and variance history reveal stagnation that a static status color alone can hide, especially over many consecutive periods.
10. A. Artifact archival preserves business cases, risk registers, and decision logs so future components can learn from prior trade-offs and risks.