MoP Practitioner common mistakes
MoP Practitioner · Understand the traps and how to avoid them.
Treating MoP as a project or programme methodology rather than a portfolio-level framework, so answers describe managing a single initiative's delivery instead of managing the collection of change.
Candidates arrive from PRINCE2, MSP or agile delivery backgrounds and default to the lifecycle and roles they know, misreading portfolio questions as delivery questions.
What to do instead
Before answering, ask 'does this option operate at the portfolio level (selection, balance, alignment across initiatives)?' and eliminate options that only make sense inside one project or programme. Practise restating each scenario in terms of the whole portfolio of change.
Confusing the portfolio definition practices (understand, categorise, prioritise, balance, plan) with the delivery practices (management control, benefits management, financial management, stakeholder engagement, organisational governance, resource management, risk management), and matching the wrong practice to a scenario.
Both sets contain similarly named activities, and scenario stems rarely name the practice outright, so candidates pattern-match on keywords such as 'prioritise' or 'risk' without checking which cycle the question sits in.
What to do instead
Memorise the two lists as distinct sets and write a one-line purpose for each practice. In practice questions, first decide whether the scenario is about deciding what should be in the portfolio (definition) or running what is already in it (delivery), then select the practice.
Selecting 'do more of everything' or 'approve all candidate initiatives' as the answer to balance or prioritisation questions, instead of recognising the need to constrain, stop or rebalance existing work.
Candidates associate portfolio management with maximising investment and approval, and miss that MoP's value lies in stopping misaligned change and reallocating constrained resources.
What to do instead
When a scenario shows over-commitment, scarce resources or shifting strategy, prefer options that involve rebalancing, deselection, phasing or stopping. Learn that the balance practice explicitly includes adjusting the mix and that prioritisation implies ranking and potentially not funding lower-ranked items.
Treating portfolio governance as identical to corporate governance or to programme governance, and failing to identify the specific role of the portfolio board, its delegated authority and its escalation route.
The governance domain overlaps heavily with organisational structures, and candidates answer with generic 'senior management oversight' rather than the portfolio-specific decision rights and escalation paths MoP describes.
What to do instead
Learn the portfolio governance model as a distinct layer: the portfolio board sets direction and makes investment decisions within delegated limits, while programme and project boards handle delivery. Practise mapping scenario symptoms (decision paralysis, unclear accountability, escalation delays) to the governance layer responsible.
Ignoring the portfolio principles when answering, and choosing technically plausible but principle-violating options, such as treating the portfolio as a one-off exercise rather than an ongoing, iterative process.
Candidates focus on practices and lifecycle content because those are more concrete, and underestimate how often questions test whether an approach is consistent with the principles.
What to do instead
Learn the principles as short testable statements (for example, that portfolio management is a continual and iterative process, and that it must be aligned with strategy and deliver measurable benefit). Use them as a checklist to reject options that imply a static, one-off or strategy-detached portfolio.
Misreading the strategic alignment principle to mean 'the portfolio should contain everything the organisation does', rather than 'the portfolio should contain the change needed to achieve strategic objectives'.
The word 'alignment' invites a broad interpretation, and candidates conflate business-as-usual operations with the portfolio of change.
What to do instead
Distinguish clearly between business as usual and the portfolio of change. When a scenario describes operational activity, exclude it from portfolio scope; when it describes change initiatives, test each against strategic objectives rather than against departmental preference.
Answering tailoring questions with a single 'correct' MoP structure instead of adapting practices to the organisation's size, maturity, culture and regulatory context.
Candidates memorise the full framework and assume exam questions reward completeness, when MoP explicitly expects proportionate application.
What to do instead
For any 'what should the practitioner do' question set in a small, low-maturity or highly regulated organisation, favour options that scale practices up or down, start simply and mature over time, and align with existing governance rather than duplicating it.
Failing to recognise the role of the portfolio office and the portfolio manager, and assigning portfolio-level decisions to programme managers or the PMO without authority.
Roles across MoP, MSP and PRINCE2 share names and responsibilities, and candidates blur the portfolio office (which supports definition and delivery practices) with a delivery-focused PMO.
What to do instead
Learn the distinct accountabilities of the portfolio manager, portfolio office, portfolio board and the SRO or business change leaders at programme level. In scenario questions, ask who has the authority and information to act at portfolio level before selecting a role.
Treating benefits management at portfolio level as simply aggregating programme benefit registers, and missing the portfolio's role in validating, prioritising and realising benefits across the whole change portfolio.
Benefit language is familiar from programme management, so candidates apply programme-level mechanics and overlook portfolio-level aggregation, dependency and dis-benefit considerations.
What to do instead
Study benefits management as a portfolio delivery practice: it covers identifying, profiling, mapping and tracking benefits across initiatives, including dis-benefits and dependencies between benefits. Practise questions that ask how the portfolio ensures benefits are realised, not just recorded.
Assuming resource management is only about headcount, and missing the portfolio's responsibility for understanding capacity, capability and constraints across the whole change portfolio, including external and shared resources.
Candidates reduce resource management to staffing a project, so they choose options about recruitment or team structure rather than about portfolio-wide capacity and supply-and-demand balancing.
What to do instead
Frame resource management as matching the demand of the portfolio of change against the supply of resources available, including skills, capability and constraints, and informing prioritisation and balance decisions. Look for options that address capacity across initiatives rather than within one.