Portfolio Strategic Alignment practice questions

Wait for the annual budget cycle to propose changes.

Why it fails: Strategic alignment is continuous, not tied to annual cycles.

multiple_choice

Why it fails: ...

Continue all projects until completion to avoid sunk costs.

Why it fails: Completion of misaligned projects wastes capital.

Reduce the portfolio budget by 10% across all projects.

Why it fails: Arbitrary cuts don't ensure strategic alignment.

Organizing the company picnic.

Why it fails: Social events have no role in analysis.

Updating the company website.

Why it fails: This is a marketing task.

Reviewing employee vacation requests.

Why it fails: This is an operational HR task, not a capacity analysis step.

Deciding on an acquisition strategy.

Why it fails: This is a high-level strategic decision.

Formulating the company's 10-year vision.

Why it fails: This is a strategic task, not operational.

Redefining the organization's core values.

Why it fails: This is a board-level strategic task.

To serve as a budget tracking tool only.

Why it fails: A portfolio strategic plan aligns the portfolio with organisational strategy, selecting and prioritising components; it does not track spend. Budget tracking belongs to portfolio financial management. Treating it as a budget tool confuses strategic alignment with cost control, so it cannot satisfy the question's focus on strategic direction.

To list all team members' contact information.

Why it fails: A portfolio strategic plan sets strategic direction, investment selection criteria and benefit alignment across the portfolio; a contact roster is administrative reference data. It is tempting because both are portfolio documents, but team contact details belong in resource or communications artefacts, not the strategic plan.

To document daily project management tasks.

Why it fails: A portfolio strategic plan aligns the portfolio with organisational strategy, defining investment criteria, prioritisation and benefits realisation; documenting daily project tasks belongs to project-level plans. It is tempting because both are planning artefacts, but operational task tracking is the remit of project schedules, not portfolio strategy.

Hire external contractors immediately without approval.

Why it fails: Hiring contractors without approval breaches portfolio governance and commits unbudgeted funds before the bottleneck's cause and options are analysed. It is tempting because adding capacity directly addresses the constraint, but contractor engagement is a resourcing decision requiring authorisation and comparison against reallocation or resequencing alternatives.

Ignore the bottleneck and continue the project as planned.

Why it fails: Ignoring the bottleneck leaves the strategic benefit unrealisable and wastes the capacity analysis that identified it. It is tempting when the constraint appears temporary or minor, but portfolio management requires the issue to be escalated and addressed through options such as reallocation, resequencing or additional approved resources.

Cancel all low-priority projects.

Why it fails: Cancelling low-priority projects discards portfolio value without first analysing the bottleneck's cause, impact or alternatives, and bypasses portfolio governance. It is tempting because freeing capacity looks decisive, yet cancellation is a last resort after options such as reallocating resources, resequencing or rebalancing the portfolio have been assessed.

Portfolio Charter Review

Why it fails: The portfolio charter defines mandate, governance and authority; it holds no data on team availability or allocation. Evaluating the constraint requires resource capacity analysis comparing supply against demand. Charter review would be the right action when validating whether portfolio scope still aligns with the authorised mandate.

Portfolio Risk Analysis

Why it fails: Risk analysis addresses uncertainty and threat exposure, not finite resource contention. The stem requires capacity versus demand comparison across projects, which resource capacity analysis or portfolio resource optimisation performs. Risk analysis would be the right tool when assessing the probability and impact of a threat materialising, such as a supplier failing.

Benefit Realization Map

Why it fails: A benefit realisation map traces dependencies between outputs, outcomes and benefits, so it cannot quantify competing demand for one engineering team. Capacity constraints are resolved through resource capacity or supply-and-demand analysis. The map would be correct when confirming that a project's outputs genuinely deliver the intended strategic benefits.

Change the project management methodology.

Why it fails: Changing the delivery methodology alters how projects are executed, not which components the portfolio contains, so misaligned components remain funded. It tempts because methodology changes are a familiar response to underperformance, and they are correct when the problem is delivery inefficiency rather than strategic misalignment.

Immediately terminate all current projects.

Why it fails: Termination is a drastic measure not supported by strategic analysis.

Request additional budget from the executive sponsor.

Why it fails: Extra budget funds components that already fail to support strategic goals, worsening the misalignment rather than resolving it. It tempts because resource constraints often block portfolio rebalancing, and additional funding is correct when aligned components are starved of the capacity needed to deliver.

Office Furniture Requirements

Why it fails: Office furniture requirements address physical workspace provisioning, not the portfolio intake criteria of strategic alignment, resource capacity, risk exposure or benefit realisation. It is tempting because facilities costs genuinely belong in portfolio budgeting and resource planning, and furniture procurement would be a legitimate consideration when assessing an office relocation or expansion component.

Vendor Marketing Materials

Why it fails: Vendor marketing materials are promotional, not evidence of feasibility, so they cannot support capability or benefit assessments. They are legitimately consulted later when shortlisting solutions, but intake feasibility requires internal capability, resource and benefit data.

Project Team Member Names

Why it fails: Team member names identify individuals, not whether the component is deliverable, so they do not inform feasibility. Names matter during resource assignment and scheduling after approval, whereas intake feasibility examines capability, capacity and strategic fit.

The Risk Register

Why it fails: The Risk Register records identified threats and responses affecting portfolio components, not the mandate for strategic goals. It is tempting because risks shape which goals are viable, and it would be the correct reference when evaluating exposure to a strategy that has already been defined.

The Resource Management Plan

Why it fails: The Resource Management Plan governs how portfolio resources are allocated and scheduled, not why strategic goals exist. It is tempting because resourcing constrains which goals are feasible, and it would be the correct reference when assessing capacity to deliver an already-defined strategy.

The Portfolio Roadmap

Why it fails: The Portfolio Roadmap sequences components and milestones over time to deliver strategy; it is derived from the goals rather than driving their definition. It is tempting because the roadmap visibly expresses strategic direction, and it would be the correct artefact when communicating how goals will be achieved.

To document all project risks.

Why it fails: Risk documentation belongs to risk management, not portfolio balancing, which reallocates investment across components to match strategy, capacity and risk appetite. Documenting risks would be the correct activity when the objective is maintaining a risk register.

To make the project schedule as short as possible.

Why it fails: Shortening schedules is a component-level scheduling concern; portfolio balancing adjusts the mix and funding of components against strategic objectives and capacity. Compressing timelines would be correct if the question asked how to accelerate delivery of a single project.

To keep all project managers happy.

Why it fails: Balancing aligns portfolio components with strategic objectives, risk appetite and resource capacity to maximise value. Keeping project managers happy is a stakeholder sentiment, not a portfolio objective, and cannot be optimised. It is tempting because morale affects delivery, but it is not the balancing goal.

Vendor invoices.

Why it fails: Vendor invoices are operational procurement records, not strategic planning inputs. The process consumes strategic objectives, organisational strategy and portfolio performance information. Invoices would be the correct focus during portfolio financial control or benefits realisation, not strategic planning.

Project team performance reviews.

Why it fails: Project team performance reviews are tactical HR artefacts, not inputs to portfolio strategic planning. That process uses organisational strategy, strategic objectives and portfolio-level information. Performance reviews would be relevant to resource management or project execution, not to setting portfolio strategy.

Individual project status reports.

Why it fails: Individual project status reports are tactical delivery artefacts, not strategic planning inputs. Portfolio strategic planning draws on organisational strategy, strategic objectives and portfolio-level performance data. Status reports would be relevant when monitoring portfolio component execution, not when setting strategic direction.

It determines the project management salary.

Why it fails: Capacity analysis examines resource availability and demand against strategic objectives; salary determination belongs to HR compensation processes. It would be correct only if the question concerned workforce cost planning, not how capability constraints guide strategic alignment.

It removes the need for prioritization.

Why it fails: Prioritization is always necessary regardless of capacity.

It automates the project selection process.

Why it fails: Capacity analysis supplies constraint data that informs selection decisions; automation of the selection process itself is a portfolio governance tooling concern. It would fit a question about workflow automation, not about how capacity insight supports strategic alignment.

Project charter.

Why it fails: A project charter authorises a single project and its project manager, not a portfolio. Portfolio authorisation comes from the portfolio charter, which grants the portfolio manager authority over resources across components. A project charter would be correct when formally initiating one project and empowering its project manager.

Business case.

Why it fails: A business case justifies investment in a component by comparing costs, benefits, and risks; it confers no formal authorisation or resource authority. Portfolio authorisation and the portfolio manager's mandate come from the portfolio charter. A business case would be correct when seeking approval to fund a specific initiative, not to authorise the portfolio itself.

Portfolio strategic plan.

Why it fails: The portfolio strategic plan defines strategic objectives, prioritisation, and investment direction; it authorises nothing and grants no resource authority. Formal portfolio authorisation and the portfolio manager's resource mandate come from the portfolio charter. The strategic plan would be correct as the guiding strategy document, not the authorising instrument.

Wait until the next fiscal year.

Why it fails: Deferring to the next fiscal year leaves the component consuming budget while delivering low strategic value for the remainder of the current cycle. Fiscal-year review suits planned annual rebalancing; this scenario demands an immediate portfolio decision to reallocate or terminate the underperforming component.

Increase the budget to help it succeed.

Why it fails: Adding budget increases investment in work already delivering low strategic value, worsening the misalignment rather than correcting it. Extra funding suits components with proven strategic contribution that are constrained by resources; here the deficiency is strategic value, not capacity or funding.

Merge it with another project.

Why it fails: Merging does not solve the underlying lack of strategic value.

Cancel the strategic initiative.

Why it fails: Cancelling discards a high-value strategic initiative over a capability gap that targeted hiring, training or partnering could close. Capacity analysis informs how to resource the initiative, not whether to abandon it. Cancellation would be correct only if the initiative no longer aligned with strategy or were unviable.

Start the project and hope for the best.

Why it fails: Proceeding without the required technical expertise leaves the capability gap unaddressed, risking delivery failure on a strategic initiative. Capacity analysis exists to surface such gaps before commitment. Hoping for the best would only be defensible if the missing expertise were genuinely immaterial to the outcome.

Outsource the entire department.

Why it fails: Outsourcing the entire department exceeds the identified gap, which concerns expertise for one initiative, and discards internal capability rather than acquiring it. Targeted sourcing or training addresses the shortfall. Full departmental outsourcing would be correct only if the whole function were being deliberately divested.

Focus on improving project team morale.

Why it fails: Team morale does not address the misalignment between the portfolio and the new cost-reduction strategy; components must be rebalanced or terminated. Morale initiatives would be the right focus when the strategy change is already reflected in the portfolio and delivery performance is suffering from disengagement.

Proceed with existing growth-focused projects.

Why it fails: Continuing growth-focused projects directly contradicts the new cost-reduction strategy, so the portfolio must be rebalanced to align with the changed strategic objectives. Proceeding unchanged would be tempting where the strategy shift is minor or growth remains a parallel goal, but here realignment is required.

Update the office dress code.

Why it fails: Dress code has no bearing on portfolio alignment with strategic objectives, so it cannot satisfy the requirement to rebalance investments toward cost reduction. Updating workplace policies would be relevant only when the strategic change specifically concerns organisational culture or employee-facing standards, not portfolio composition.

To list the office holiday schedule.

Why it fails: Holiday schedules are administrative calendar data, carrying no component sequencing or strategic intent. The Portfolio Roadmap exists to communicate how initiatives and investments align to strategy over time, so it would be selected when stakeholders require that forward-looking, prioritised delivery view.

To track daily task assignments.

Why it fails: Daily task assignments belong to project schedules or work management tools, not portfolio-level planning. A Portfolio Roadmap sequences components and capability delivery across time horizons to show strategic alignment and dependencies, which is why it would be chosen when executives need that multi-year investment view.

To serve as an audit trail for project expenses.

Why it fails: Expense audit trails sit with financial systems and accounting records, not portfolio planning artefacts. The Portfolio Roadmap maps components against strategic objectives and timelines to guide investment decisions, making it the choice when leadership needs that alignment and sequencing picture.

Split resources 50/50 between the projects.

Why it fails: An even split ignores strategic weighting: portfolio management ranks initiatives by alignment and value, then allocates capacity accordingly. Equal division is tempting as impartial, but it dilutes the higher-priority initiative and satisfies neither, whereas governance-driven prioritisation resolves the conflict deliberately.

Let the resource managers fight it out.

Why it fails: Leaving resource managers to compete ignores the portfolio governance layer, which prioritises initiatives against strategic objectives and formally reallocates shared capacity. It appeals as empowerment, yet escalation to the portfolio board is what resolves cross-initiative contention; unmanaged competition simply entrenches the strongest manager's influence.

Cancel both projects.

Why it fails: Cancelling both initiatives discards strategic value and delivers nothing toward portfolio objectives; the conflict concerns capacity allocation, not project viability. It is tempting as a decisive reset, but portfolio governance instead reprioritises, phases, or reallocates resources so the higher-value initiative proceeds.

How many people are on the project team?

Why it fails: Team size is a resourcing metric, revealing nothing about whether the component advances organisational objectives, which is what strategic fit assesses. It is tempting because headcount indicates delivery capacity, and team size would be the correct consideration when assessing resource availability or staffing feasibility.

Will this project win an award?

Why it fails: Awards measure recognition, not alignment with organisational objectives, so the question cannot assess strategic fit. It is tempting because awards signal quality and prestige, and award criteria would be the correct consideration when evaluating a component's external recognition or marketing value.

Is this the cheapest project to implement?

Why it fails: Strategic fit asks whether a component advances organisational objectives, not whether it is cheapest; cost is a financial feasibility concern. It is tempting because budget pressure makes cost feel decisive, and it would be correct if the question asked how to rank components by affordability within a constrained funding envelope.

Project manager.

Why it fails: A project manager delivers an individual project within agreed scope, schedule and budget; they do not define strategy across the portfolio. This would be the right answer if the question asked who is responsible for day-to-day execution and delivery of a single project's objectives.

Portfolio manager.

Why it fails: The portfolio manager executes and monitors the portfolio — balancing components, optimising resource allocation and reporting performance — rather than setting its strategic direction. That role would be the answer if the question asked who manages portfolio delivery and governance activities on an ongoing basis.

IT department head.

Why it fails: An IT department head owns technology delivery and operational resourcing within one function, not enterprise-wide portfolio strategy, which spans all business units. This would be correct if the question concerned who provides technical direction or staffing for IT projects rather than the strategic vision guiding the whole portfolio.