Portfolio Governance practice questions

Portfolio Manager

Why it fails: The PM creates it, but the Governance Committee approves it.

Project Management Office (PMO) Director

Why it fails: The PMO supports, but does not own, the portfolio governance.

Portfolio Sponsor

Why it fails: The sponsor is an advisor; the committee is the governing body.

The grocery shopping list for the office breakroom.

Why it fails: Irrelevant.

The social media profiles of the project staff.

Why it fails: Irrelevant.

The current weather forecast.

Why it fails: Irrelevant.

To document the results of portfolio audits.

Why it fails: Audit results are recorded in portfolio reports and review logs, not the roadmap, which sequences components against strategic timeframes. It is tempting because audits inform roadmap updates, but documenting their outcomes is a governance activity, not the roadmap's primary function.

To serve as a detailed project schedule for team members.

Why it fails: The roadmap shows sequencing and dependencies across the portfolio at a strategic horizon, not task-level schedules owned by project managers. It is tempting because roadmaps do convey timing, but detailed team schedules belong in project plans.

To authorize individual project budgets.

Why it fails: Budget authorisation comes through portfolio governance and funding decisions, not the roadmap, which communicates component sequencing and strategic alignment. It is tempting because roadmap components carry indicative investment, but authorising individual project budgets is a separate approval process.

Sanction the project managers for non-compliance.

Why it fails: Sanctioning addresses the individuals rather than the governance gap, and the audit finding is about template adoption, not misconduct. It is tempting because it signals enforcement, but disciplinary action would be the right response only where deliberate non-compliance persists after corrective and training steps have already failed.

Manually update all reports to comply with the standard.

Why it fails: Manually rewriting reports treats the symptom, not the cause, and leaves the non-standard practise recurring after the audit closes. It is tempting because it restores immediate compliance, but manual correction would be the right action only for a one-off reporting error, not a systemic deviation from the Portfolio Governance Plan.

Ignore the finding if the projects are still achieving their KPIs.

Why it fails: KPI achievement does not satisfy the Portfolio Governance Plan's reporting requirement, so the deviation remains unresolved and recurs. It is tempting because performing projects appear healthy, but taking no action would be the right choice only where the audit finding is immaterial and the plan explicitly permits alternative reporting formats.

Issue a change request for every active component.

Why it fails: Portfolio governance responds to regulatory shifts by realigning components, priorities and investment criteria at portfolio level, not by raising a change request per component; that treats a strategic realignment as routine component-level change control. Change requests suit individual scope, schedule or cost variations within a component, not portfolio-wide reprioritisation.

Ignore the regulation until the next annual portfolio review cycle.

Why it fails: Deferring to the annual review leaves portfolio components misaligned with the regulation for months, breaching compliance obligations. Governance exists to re-evaluate and re-prioritise components when strategic drivers change, so the portfolio manager should initiate an out-of-cycle review now.

Re-authorize all components using the existing charter.

Why it fails: Re-authorising components under existing charters assumes the current strategic alignment still holds, so it cannot reflect the regulation's new priorities. The portfolio manager must revise the governance criteria and re-evaluate components against the changed priorities before re-authorising them.

Conduct an audit of the component's project management plan.

Why it fails: Auditing the project management plan examines process compliance, not whether the component still delivers expected portfolio value. It is tempting because audits are a familiar governance control. An audit is the correct response when the concern is execution quality or adherence, not strategic value erosion.

Immediately terminate the component to save budget.

Why it fails: Terminating immediately skips the portfolio governance step of evaluating the component's continued alignment with strategic objectives before recommending a decision. It is tempting when budget pressure dominates. Immediate termination is the correct action only after analysis confirms the component no longer supports portfolio strategy and reallocation is approved.

Update the portfolio roadmap to reflect delayed timelines.

Why it fails: Adjusting roadmap timelines addresses schedule slippage, not the stakeholders' concern about value delivery. It is tempting because roadmap updates are a routine governance output. The roadmap is the correct artefact to revise when the issue is timing, whereas a value shortfall requires assessing the component against strategic objectives first.

Delegate all decisions to the project managers.

Why it fails: Delegating every decision to project managers strips the portfolio board of its investment-gating authority, so strategic alignment and cross-project prioritisation are lost. It is tempting because it removes committee latency, but that speed is only appropriate where decisions are purely operational and carry no portfolio-level funding or risk impact.

Remove all governance reviews to reduce overhead.

Why it fails: Removing all governance reviews eliminates the investment gates that authorise funding and prioritisation, so decisions become unaccountable rather than rapid. It is tempting because overhead visibly drops, but that trade-off only fits small, low-risk portfolios where a single sponsor can absorb every approval.

Increase the frequency of governance committee meetings.

Why it fails: Meeting more often adds governance touchpoints rather than removing them, so decision latency grows instead of shrinking. It is tempting because frequent reviews feel responsive, yet that approach suits high-risk portfolios needing tighter oversight, not one whose stated goal is rapid decision-making through streamlined authority.

Add it to the roadmap and inform the governance committee later.

Why it fails: Adding the project first and notifying governance afterwards inverts portfolio change control, letting unapproved work consume resources before scrutiny. It is tempting because it appears decisive and keeps delivery moving, and would suit a minor in-roadmap adjustment delegated to the portfolio manager.

Approve it if the project has sufficient budget.

Why it fails: Budget availability alone does not authorise work outside the approved roadmap; portfolio authorisation requires evaluation against strategic objectives and governance approval. It is tempting because funded proposals feel low-risk, and approving within budget would be reasonable for an in-roadmap project with confirmed funding.

Reject the proposal immediately as it is not on the roadmap.

Why it fails: Immediate rejection ignores the portfolio change-control process, which exists to evaluate unplanned proposals on strategic fit, resource capacity and risk before deciding. It is tempting because roadmap alignment matters, and rejection would be right for a proposal already assessed and found misaligned with strategy.

Conduct a portfolio audit to verify historical data integrity.

Why it fails: Auditing historical data integrity checks past records, not whether the charter's objectives match current organisational strategy. It is tempting because audits are governance activities and can validate alignment retrospectively, but the charter is being finalised now, so alignment requires strategic review at this point, not historical verification.

Update the portfolio roadmap with current resource availability.

Why it fails: Roadmap updates address scheduling and resource allocation, not strategic alignment of the charter's content. It is tempting because roadmaps translate strategy into delivery timing, so updating one feels governance-related, but alignment is established by reviewing the charter against strategic objectives before approval, not by refreshing resourcing detail.

Execute a portfolio component authorization process.

Why it fails: Component authorisation governs whether individual initiatives proceed, which happens after the charter exists and strategy is already set. It is tempting because authorisation is a core governance control, but it operates downstream; charter alignment is assured by validating the charter's content against organisational strategy during its development.

Governance Review Report

Why it fails: A Governance Review Report documents findings from an evaluation of existing governance; it does not establish the authority, decision rights or policies that constitute the foundation. It is tempting because governance artefacts are its subject, but it is an output of assurance activity, not the baseline document that defines governance.

Portfolio Strategic Plan

Why it fails: The Portfolio Strategic Plan defines portfolio components, investment mix and strategic alignment, not the decision rights, policies and escalation paths that governance requires. It is tempting because strategy shapes what governance oversees, but the governance framework itself is documented in the Portfolio Management Plan, which this option does not provide.

Project Management Plan

Why it fails: The Project Management Plan governs delivery of a single project's scope, schedule and cost, not portfolio-level governance. It tempts because it is a familiar governing document, and it would be correct when directing execution within one project, whereas portfolio governance rests on the portfolio management plan and strategic alignment.

By authorizing the next year's budget.

Why it fails: Budget authorisation is a governance decision made through funding and approval processes, not an audit finding. It is tempting because audits surface financial variance data that feeds budgeting, but the audit itself verifies conformance rather than granting next-year funding.

By enforcing project management compliance with technical standards.

Why it fails: Portfolio audits assess portfolio-level alignment, value delivery and governance effectiveness, not individual project adherence to technical standards, which is project quality assurance. It is tempting because both involve compliance checking, but technical standards sit within project execution, not portfolio governance.

By selecting new projects for the portfolio.

Why it fails: Portfolio audits review performance, alignment and governance adherence of existing components; project selection happens through portfolio optimisation and prioritisation. It is tempting because audits inform decisions, but selection is an authorisation activity, not an audit output.

To prevent project managers from speaking to the executive committee.

Why it fails: Tiered governance exists to match decision rights and oversight intensity to investment size, risk and strategic alignment, so low-value items bypass executive review. Blocking project managers from the executive committee is not its purpose; that would be an access-control or escalation-path decision, and it would also remove the upward visibility tiering is designed to preserve.

To reduce the number of employees required in the PMO.

Why it fails: Tiered governance scales decision rights and oversight according to initiative risk and value; it does not reduce PMO headcount, and staffing levels are unaffected by how governance layers are structured. It is tempting because lighter governance for low-risk work can appear to cut administrative effort, and would be correct if the objective were streamlining PMO workload.

To comply with outdated regulatory requirements.

Why it fails: Tiered governance exists to match oversight rigour to each initiative's risk, value and complexity, not to satisfy legacy regulatory mandates; compliance obligations apply uniformly regardless of tiering. It is tempting because governance is often associated with regulatory conformance, and would be correct if the driver were meeting a specific external compliance requirement.

Replace the project managers.

Why it fails: Replacing project managers addresses delivery performance, not the roadmap-to-execution gap the manager must diagnose first. It is tempting because poor delivery is visible, and replacing managers would be right if evidence showed consistent execution failure by those individuals.

Update the roadmap immediately to reflect current status.

Why it fails: Rewriting the roadmap to match current status masks the variance instead of identifying its cause, destroying the baseline needed for comparison. It is tempting because it produces immediate visual consistency, and updating a roadmap would be right after the underlying misalignment has been diagnosed and approved.

Increase the portfolio budget to get projects back on track.

Why it fails: Additional funding does not reconcile a roadmap with actual execution; misalignment may stem from scope, dependencies or prioritisation, not resourcing. It is tempting because budget shortfalls do delay delivery, and increasing funding would be right if analysis confirmed resource constraints caused the drift.

The total budget of the entire organization.

Why it fails: Evaluation uses the component's alignment with strategic objectives and its contribution to portfolio balance, not the organisation's total budget. Total budget tempts as a funding ceiling, but affordability is one constraint; authorisation weighs expected benefits and risk against strategy, not merely available funds.

The personal preferences of the executive committee members.

Why it fails: Portfolio authorisation compares the component's cost-benefit analysis against strategic objectives and portfolio balancing criteria, not individual executives' preferences. Personal preference tempts because executives do approve components, but governance requires documented, objective alignment rather than subjective opinion.

The project team's past performance records.

Why it fails: Past performance records inform historical capability, but authorisation evaluates the submitted cost-benefit analysis against strategic objectives and portfolio balance. Performance history tempts because it predicts delivery capability, yet it cannot justify whether the component's benefits merit inclusion in the portfolio.

To execute the individual tasks on the roadmap.

Why it fails: The Governance Committee provides oversight, decision-making and endorsement of the portfolio roadmap; executing individual roadmap tasks is delivery work owned by component and project teams. It is tempting because committee members are accountable for portfolio outcomes, and would be correct if the question asked who authorises or approves roadmap execution rather than who performs it.

To create the detailed project schedules.

Why it fails: Detailed project schedules are produced by project managers and delivery teams; the Governance Committee reviews and endorses the portfolio roadmap at a strategic level. It is tempting because the committee approves portfolio components, and would be correct if the question concerned authorising a component's inclusion rather than building its schedule.

To perform the daily data entry for the roadmap.

Why it fails: Daily data entry is an operational task performed by analysts, not a governance body; the committee sets strategic direction, prioritisation and funding decisions for the roadmap. It is tempting because committees do oversee roadmap content, but that oversight means approving and steering, not manually maintaining records.

Ask the project manager to improve the report format.

Why it fails: A failed governance review concerns the component's performance, alignment or benefits, not the report's presentation; reformatting documentation leaves the underlying issues unresolved. It tempts because poor reporting can obscure status, so improving it is valid when the review fails specifically due to inadequate or misleading information.

Terminate the project immediately.

Why it fails: Some issues may be remediable.

Continue the project as it is already underway.

Why it fails: Continuing a component that failed governance review ignores the decision gate's purpose and compounds sunk cost. It is tempting when delivery is underway, but governance exists to authorise, redirect or terminate; the review outcome should drive re-planning, remediation or cancellation.

Bypass the governance steps to speed up delivery.

Why it fails: Bypassing governance removes the stage-gate reviews and decision checkpoints that authorise continued funding, so the portfolio loses its control mechanism and audit trail. It tempts because it appears to clear the delay quickly, and would be right only if the framework itself were the identified root cause and formally amended.

Add more staff to the governance committee to speed up decisions.

Why it fails: Enlarging the committee increases the number of approvers, which lengthens quorum and consensus time rather than removing the restrictive gate itself. Adding members suits portfolios where decision capacity, not governance rigidity, is the constraint — for example, a single overwhelmed review board handling excessive volume.

Accept the delays as part of the price of governance.

Why it fails: Accepting delays leaves the identified governance bottleneck unaddressed, so the portfolio keeps absorbing schedule slippage rather than resolving it. Tolerating governance overhead is defensible only where regulation or audit mandates fixed checkpoints that cannot be streamlined; here the framework is merely over-restrictive, so the manager should propose tailoring it through the governance board.

Maintaining a static Portfolio Charter.

Why it fails: A frozen charter cannot reflect revised strategic priorities, so alignment with market shifts is lost. Chartering is genuinely useful at portfolio formation, when components are first authorised and mapped to strategic objectives, which is why freezing it appears prudent.

Strictly adhering to the initial project plan.

Why it fails: A static baseline cannot respond to shifting market conditions; portfolio governance requires periodic rebalancing against strategic objectives. Clinging to the original plan is tempting because baselines do control scope on individual projects, where deviation from an approved plan is a change to be managed.

Limiting the number of components in the portfolio.

Why it fails: Capping component count controls portfolio size and resource concentration, not alignment with shifting market conditions; rebalancing and reprioritisation review is what realigns the portfolio when markets change, making this a governance technique for a different objective.

Portfolio Governance Committee

Why it fails: The Portfolio Governance Committee approves portfolio decisions and investment gates, but the portfolio manager owns and maintains the roadmap itself. Governance is tempting because the committee ratifies prioritisation and funding, which is correct when the question asks who approves roadmap changes rather than who is responsible for producing it.

Project Management Office (PMO) lead

Why it fails: The PMO lead supports roadmap maintenance and reporting but holds no portfolio decision authority; accountability sits with the portfolio manager. PMO involvement is tempting because PMOs often own the roadmap artefact and facilitate its updates, which is correct when the question concerns documentation or process governance rather than ownership.

Portfolio Sponsor

Why it fails: The Portfolio Sponsor funds and champions the portfolio but does not own the roadmap; the portfolio manager maintains and updates it. Sponsorship is tempting because sponsors approve strategic direction and investment, which would be the answer if the question asked who authorises roadmap changes or resolves escalated portfolio-level conflicts.

To fire underperforming project managers.

Why it fails: Governance audits evaluate portfolio processes, alignment and compliance, not individual performance management; dismissing project managers is an HR disciplinary action outside the audit's remit. It is tempting because audits can reveal poor project outcomes, and would be correct if the goal were personnel performance review rather than governance assurance.

To assign new tasks to the team.

Why it fails: Assigning tasks is operational resource management performed by project managers; governance audits examine decision-making structures, compliance and benefit realisation, not day-to-day work allocation. It is tempting because audits may surface resourcing gaps, and would be correct if the objective were team workload distribution rather than governance oversight.

To increase the budget of the projects.

Why it fails: Governance audits assess alignment, compliance and value delivery against strategic objectives; they do not allocate or increase project budgets, which is a portfolio funding decision. It is tempting because audits can recommend reallocation, and would be correct if the goal were financial planning rather than governance assurance.