8.4: PfMP style questions

Sample Questions

1. An enterprise portfolio review board establishes variance thresholds for all active initiatives. The approved governance policy states that any component exhibiting a CPI between 0.95 and 0.90 is categorized in the Yellow Band, while a CPI below 0.90 requires a formal Red Band escalation. During the Month 3 review of a $4,000,000 core payments overhaul, the portfolio dashboard indicates that the component has a CPI of 0.92, which has held steady for 60 consecutive days without improving. According to portfolio governance best practices, how should the portfolio manager handle this component?
   1. Ignore the status, because the component remains within the allowable Yellow Band and has not crossed below the 0.90 Red threshold.
   2. Escalate the component to the Portfolio Review Board under a temporal tripwire rule, because lingering in a warning state for over 45 days indicates that operational self-correction has stalled.
   3. Unilaterally terminate the component immediately to prevent further capital degradation.
   4. Reallocate $500,000 from the enterprise Management Reserve without board approval to artificially restore the CPI to 1.0.
2. A portfolio manager conducts root-cause triage on a struggling $1.8M customer portal initiative that has breached the Red cost variance threshold (CV = -$240,000). Forensic investigation reveals that the engineering team's delivery velocity has dropped significantly because 60% of their pull requests are failing automated integration testing, driven by inexperienced junior developers hired during an aggressive scale-up. Applying the root-cause triage framework, which governance determination should the portfolio manager submit to the steering committee?
   1. The variance is a temporary startup expenditure; recommend taking no action and allow the S-curve to normalize naturally.
   2. The variance is an unrecoverable force majeure event; recommend immediate project termination and write down all completed software assets.
   3. The variance is driven by a non-self-correcting internal capability deficit; recommend an intervention to inject experienced engineering talent or specialized consultants to stabilize velocity within a recalibrated baseline.
   4. The variance is driven by an external supply-chain shock; recommend filing a breach-of-contract lawsuit against the cloud hosting vendor.
3. An executive steering committee faces a sudden enterprise cash crunch due to macro credit tightening. The CEO demands that every business unit execute an immediate, across-the-board "flat 12% budget cut" across all active projects to meet the cash-preservation target. As the portfolio manager, what governance concept should you present to the CEO to challenge this approach?
   1. The Flat-Cut Fallacy; demonstrate that across-the-board cuts penalize lean, high-performing strategic assets while starving mandatory regulatory work, recommending instead an asymmetric capital rationing approach based on the 2x2 Mandatory/Discretionary matrix.
   2. Little's Law; demonstrate that cutting project budgets increases work-in-progress inventory across all sprint queues.
   3. The Delphi Technique; run three rounds of anonymous expert questionnaires before making any spending reductions.
   4. The Law of Diminishing Returns; explain that reducing funding on any project automatically increases its net present value.
4. A portfolio review board assesses the fate of four troubled components during an annual portfolio rebalancing review: Component Alpha, a non-discretionary statutory compliance engine required to maintain the enterprise's banking license; Component Beta, a discretionary tactical marketing automation tool; Component Gamma, an exploratory strategic machine-learning initiative; and Component Delta, an internal corporate intranet redesign. Applying the Multi-Factor Component Fate Framework, which sequence of component disposition should the portfolio manager recommend?
   1. Terminate Alpha first; protect Beta, Gamma, and Delta.
   2. Terminate Beta and Delta (Discretionary/Tactical) first; pause or pace Gamma (Discretionary/Strategic); re-scope and protect Alpha (Mandatory/Tactical).
   3. Apply a flat 25% budget reduction across Alpha, Beta, Gamma, and Delta equally.
   4. Surrender the banking license associated with Alpha to allocate all enterprise capital to Beta.
5. An enterprise portfolio includes a multi-year CRM deployment that has consumed $14M of its original $16M capital authorization. The program is 18 months behind schedule, user adoption pilots have failed, and the target architecture has been made largely redundant by a newly acquired subsidiary's cloud platform. The business sponsor demands an emergency $5M capital tranche, arguing that canceling now would waste the $14M already invested. What decision trap is the sponsor exhibiting, and how must the portfolio governance board rule?
   1. The sponsor is exhibiting the Halo Effect; the board should grant the $5M unconditionally.
   2. The sponsor is succumbing to the Sunk-Cost Fallacy; the board should ignore the historical $14M spend, evaluate the remaining cost-to-complete against the forward-looking Net Present Value, and terminate the initiative to prevent further capital waste.
   3. The sponsor is demonstrating Process Fluency; the board should reward their commitment by doubling the project budget.
   4. The sponsor is correctly applying Earned Value principles; the board must always fund any project that has completed more than 80% of its planned duration.
6. A high-tech consumer electronics portfolio contains a project with a $1,200,000 budget planned evenly across 12 months. At the end of Month 2, actual cumulative expenditures reach $215,000, representing a $15,000 cost overrun against the $200,000 baseline. The portfolio manager discovers that the overrun was caused by a planned upfront bulk purchase of specialized development hardware and automated testing rigs required for the whole year. Applying the root-cause triage framework, what is the appropriate classification of this variance?
   1. A fatal structural variance requiring an emergency project shutdown.
   2. A temporary, recoverable variance driven by front-loaded capital deployment that will naturally normalize along the planned S-curve by Month 4, requiring monitoring rather than executive intervention.
   3. A fraudulent accounting transaction requiring an immediate forensic audit of the development team.
   4. A scope rupture requiring the project to be reclassified as a Could-Have initiative.
7. A fintech portfolio manager applies a 2x2 Capital Rationing Grid to categorize corporate initiatives. A newly passed federal open-banking statute imposes strict data-sharing security mandates on the enterprise, carrying severe daily financial fines and criminal penalties for non-compliance within 180 days. How should this initiative be classified within the 2x2 portfolio capital rationing framework?
   1. Discretionary and Strategic.
   2. Mandatory and Tactical.
   3. Discretionary and Expense.
   4. Could-Have and Peripheral.
8. During a corporate portfolio restructuring, the COO requests that the PMO keep struggling projects in "deferred status" indefinitely rather than formally closing them, arguing that write-offs damage employee morale. What foundational principle of strategic portfolio management should the portfolio director articulate to counter this recommendation?
   1. Formal component closure and decisive write-offs are vital to free up captive financial capital and human bandwidth for higher-value investments, ensuring the portfolio reflects current strategy rather than unmanaged historical commitments.
   2. Deferred projects do not consume any balance-sheet capacity, so keeping them open indefinitely has zero financial impact.
   3. Projects should never be closed because unspent capital automatically rolls over into executive bonus pools.
   4. Every project ever chartered by an organization must be driven to 100% operational deployment to satisfy ISO 9001 certification.
9. An industrial conglomerate evaluates a proposed $10M warehouse robotics automation component. It is strategically discretionary, and the internal systems integration engineering team is currently running at 115% utilization across two higher-priority mandatory compliance programs. Applying capacity-gated capital rationing logic, what governance disposition should the review board assign to this component?
   1. Authorize the component immediately and mandate 80-hour workweeks for the engineering team.
   2. Cancel the mandatory compliance programs to free up integration engineers for the robotics project.
   3. Freeze or reject the component; do not authorize discretionary initiatives when internal capacity is constrained by higher-priority mandatory work.
   4. Classify the component as a Must-Have asset without altering its strategic justification.
10. A telecommunications portfolio manager presents a strategic realignment proposal to the executive governance board. A flagship 5G mobile application initiative has executed with pristine operational metrics (CPI = 1.02, SPI = 1.01). However, the corporate executive committee recently pivoted the enterprise strategy from retail consumer subscriber growth to B2B enterprise private-network infrastructure. How should the portfolio review board govern the fate of the 5G mobile application component?
    1. Keep funding the mobile application through full deployment, because canceling an initiative with green execution metrics violates governance ethics.
    2. Execute an orderly strategic component closure and write-off; the component's strategic relevance has evaporated despite its flawless execution, and continuing it wastes resources that should be redirected to the B2B private-network strategy.
    3. Force the program manager to rewrite the mobile app's source code into a B2B network routing protocol without adjusting the schedule baseline.
    4. Escalate the project to the CEO for disciplinary reprimand of the delivery team.

Answer Key

1. B. A component lingering in a warning band for over 45 days without recovery indicates stalled self-correction and warrants escalation to the review board.
2. C. A non-self-correcting internal capability deficit calls for a targeted intervention, such as injecting experienced talent, rather than waiting or blaming external factors.
3. A. The Flat-Cut Fallacy penalizes lean, high-performing and mandatory work equally with bloated discretionary programs, so cuts should be asymmetric based on mandatory/discretionary status.
4. B. The Multi-Factor Component Fate Framework cuts discretionary/tactical work first, paces discretionary/strategic work, and protects mandatory components that sustain the license to operate.
5. B. The sponsor is exhibiting the Sunk-Cost Fallacy; the board should evaluate only the forward-looking cost-to-complete and NPV, not past spend.
6. B. A planned upfront bulk purchase creates a temporary, recoverable variance that normalizes along the S-curve rather than signaling structural failure.
7. B. A statutory deadline with severe penalties is Mandatory because compliance is unavoidable, and Tactical because it requires near-term execution.
8. A. Formal closure and write-offs free up captive capital and talent for higher-value work, keeping the portfolio aligned with current strategy.
9. C. Capacity-gated rationing requires freezing or rejecting discretionary work when internal capacity is already constrained by higher-priority mandatory programs.
10. B. Flawless execution metrics do not justify continued funding once strategic relevance has evaporated, so the component should be closed and resources redirected.