Management of Portfolios: Purpose, Scope and Structure
This domain tests whether you understand what portfolio management is for, how it differs from programme and project management, and how MoP separates definition from delivery. Questions often ask you to classify an activity or challenge a weak portfolio approach.
What MoP means by a portfolio
MoP defines portfolio management as a coordinated collection of strategic processes and decisions that together enable the most effective balance of organizational change and business as usual. A portfolio is therefore the organization's total investment in change, not a reporting tier above projects. It answers two questions: are we doing the right things (definition), and are we doing them right (delivery)?
Core rules
- Portfolio management covers change and its relationship with BAU; excluding BAU destroys the capacity and balance analysis.
- Programmes and projects deliver; the portfolio selects, prioritizes, balances and governs the investment.
- The portfolio is defined by strategic scope, not by organizational chart; one organization may have several portfolios.
- Decision-making, not data collection, is the centre of the discipline.
Worked example
A retailer has 40 projects and 8 programmes. The CFO asks for a “portfolio of all approved projects” and proposes a weekly status pack. Reasoning: a status pack supports management control, but portfolio management starts earlier. The team must understand strategic objectives and BAU demand, categorize initiatives, prioritize against agreed criteria, balance risk and resource, and plan funding and capacity. Only then does control reporting make sense.
Traps
- Equating the portfolio with every approved project.
- Treating portfolio management as scheduling or reporting.
- Confusing portfolio (strategic investment) with programme (related projects) or project (single deliverable).
- Assuming a portfolio must be enterprise-wide.