Why Your Project Keeps Getting Reprioritised
If you have ever had a project paused mid-stream, had your resource allocation suddenly cut, or been told that the scope needs to shrink because “the business has other priorities,” you have already felt the effects of project portfolio management, even if nobody used that term. Understanding what project portfolio management is, and how it operates above the level of individual projects, is one of the most practically useful things a BA or PM can do to make sense of the decisions that affect their work daily.
Project portfolio management (PPM) is the discipline by which an organisation selects, prioritises, funds, and governs a collection of projects and programmes to maximise the return on its investment in change. It is not about managing a single project well. It is about managing the whole body of change activity as a coherent whole, aligned to strategy. When a senior leader tells your project sponsor that the budget has been reallocated, that decision came from somewhere in the PPM process, whether that process is mature and formal or improvised around a spreadsheet.
How PPM Connects to Individual BA and PM Work
The reason BAs and PMs need to understand PPM is not because they will usually run it. It is because PPM is the source of the constraints, priorities, and strategic context that shape everything they do at project level. Scope boundaries, mandatory integration points, deadlines tied to regulatory cycles, and sudden requests to demonstrate benefits early: all of these are often portfolio-level decisions landing on individual projects without much explanation.
When I worked on a large asset management system procurement for a government utilities client (Organisation A), the project team was repeatedly frustrated by requirements that seemed to shift in priority between review cycles. What became clear to me was that the organisation was running a parallel financial systems replacement programme, and the two projects were competing for the same ICT infrastructure and the same senior stakeholder time. The portfolio governance body was making trade-offs between the two programmes every quarter, and those trade-offs were showing up as scope adjustments and deferred modules in our project. Nobody on the delivery team had been briefed on this dynamic. Once I understood it, I could advise the project sponsor to present our requirements in terms of what could be phased to reduce ICT dependency, which is exactly what unlocked the next tranche of budget approval.
Understanding PPM gave me the language and the framework to navigate that constraint. Without it, I would have kept writing requirement statements into a vacuum and wondering why prioritisation decisions seemed arbitrary.
The Key Components of a Project Portfolio
A portfolio is not just a list of projects. It has structure, governance, and a set of management disciplines that operate across all projects simultaneously. Here is what those components look like in practice:
- Portfolio governance: A decision-making body, often a portfolio board or investment committee, that reviews and approves which projects are initiated, continued, paused, or cancelled based on strategic fit and available resources.
- Prioritisation framework: A scoring or weighting mechanism that ranks competing project proposals against strategic objectives, risk, cost, and expected benefit so that the portfolio board can make defensible investment decisions.
- Resource capacity planning: An organisation-wide view of available people, budget, and infrastructure so that the portfolio does not overcommit. This is where BA and PM resource pools get allocated and sometimes competed over.
- Benefits realisation tracking: A process for measuring whether completed projects actually delivered what was promised in their business cases, feeding back into future prioritisation decisions.
- Portfolio reporting: Regular status reporting across all projects in the portfolio, usually aggregated into a dashboard that senior leaders use to identify at-risk investments and make intervention decisions.
PPM vs Programme vs Project: What Is the Difference
One of the most common sources of confusion for BAs and PMs is where portfolios, programmes, and projects sit relative to each other. The table below sets this out clearly.
| Level | Focus | Typical Decision-Maker | BA or PM Role |
|---|---|---|---|
| Portfolio | Which work should the organisation invest in to deliver its strategy? | Executive leadership, investment committee | Rarely involved directly; subject to portfolio decisions |
| Programme | How do we coordinate a group of related projects to deliver a capability or benefit? | Programme director, programme board | BA may contribute to programme-level requirements; PM may manage a project stream |
| Project | How do we deliver a defined scope within time and budget? | Project sponsor, project board | Core delivery role for both BA and PM |
The practical implication of this structure is that when you are working at project level, you are operating within constraints that were set at portfolio and programme level. Scope decisions, integration requirements, delivery timelines, and even the governance gates your project must pass through are largely inherited from above. Understanding this saves you enormous frustration when decisions seem to arrive from nowhere.
What PPM Means for Requirements and Scope
For BAs specifically, the portfolio layer has a direct impact on requirements work. When an organisation runs a structured PPM process, projects are initiated on the basis of approved business cases. Those business cases contain high-level benefit statements and investment boundaries that effectively pre-shape the scope of what the BA will be asked to elicit and document. If you arrive on a project without reading the approved business case, you are working without the strategic context that justifies the project’s existence.
I have seen this cause serious problems on more than one occasion. On a health sector project (Project X), a BA team spent three months eliciting detailed requirements for a patient referral workflow that included real-time integration with a third-party clinical system. When the requirements went to the portfolio governance board for the gate review, it became apparent that the integration had been explicitly excluded from the approved business case scope because the third-party system was itself scheduled for replacement in the following financial year. The BA team had not been given access to the business case. The portfolio governance process had not communicated its decisions to the delivery team. The result was a requirements document that had to be substantially rewritten and a delivery timeline that slipped by two months.
The friction point here was a sponsor who had informally expanded scope in workshops without acknowledging that the portfolio governance body had already drawn the boundary. Understanding PPM would not have prevented this entirely, but it would have prompted the BA lead to ask the right questions at kick-off: what does the approved business case say, and has this project passed its initiation gate?
If you want a practical starting point for structuring that early-stage thinking, the article on how to start a business analysis project covers what to do before you run your first workshop.
How PPM Creates Strategic and Tactical Disconnect
The disconnect between strategy and delivery is one of the most persistent problems in change management, and PPM is both the cause and the potential cure. When PPM is immature, organisations approve too many projects for the resources they have, do not maintain clear strategic rationale for each project, and fail to communicate portfolio-level decisions back to delivery teams. The result is what most experienced BAs and PMs recognise immediately: a portfolio of projects that are each individually justified but collectively incoherent, competing for the same people and making conflicting demands on the same systems.
When PPM is well run, it creates strategic clarity at the delivery level. Projects arrive with clear mandates, defined integration boundaries, and realistic resource allocations. Scope changes go through a structured change control process that considers portfolio-wide implications, not just project-level impact. This is the environment where scope creep and governance can be managed properly rather than fought case by case.
For PMs, mature PPM also means that escalations have somewhere meaningful to go. When a project is being blocked by resource competition from another project in the portfolio, a portfolio governance body can adjudicate. Without that structure, PMs are left negotiating informally with other project managers with no mechanism for resolution.
Practical Ways BAs and PMs Can Engage with PPM
Even if you are not invited to sit on the portfolio board, there are concrete things you can do to work more effectively within a PPM context:
- Read the approved business case before you start requirements elicitation. The business case sets the strategic rationale and investment boundary for your project, and it will tell you what the portfolio governance body has already decided about scope.
- Identify your project’s dependencies on other portfolio projects. Find out which other projects are running concurrently and whether your project shares infrastructure, stakeholders, or data with any of them. This is essential groundwork that the kick-off meeting questions article covers in detail.
- Frame requirements and scope changes in terms of business benefit. Portfolio governance bodies respond to benefit and risk arguments, not feature lists. If you need to escalate a scope decision, express it in the language of the portfolio: what strategic objective is at risk, and what is the cost of not acting?
- Understand the governance gates your project must pass. Most PPM frameworks include stage gates where the portfolio board reviews project progress before releasing further funding. Know when those gates are, what evidence is required, and make sure your BA artefacts are gate-ready.
- Track benefits realisation, not just delivery. PPM depends on accurate benefits data to make future prioritisation decisions. If you are involved in post-implementation review or benefits tracking, treat that work seriously rather than as an afterthought.
Where BA Career Development Connects to PPM Understanding
Senior BAs and those moving into business architecture or strategy roles will find that PPM literacy is increasingly expected. As organisations invest in enterprise-level change governance, they need people who can translate between the strategic intent captured in portfolio decisions and the operational detail of delivery. BAs who understand PPM can take on portfolio analyst roles, support investment committee secretariats, and contribute to business case development in a way that junior BAs cannot. If you are thinking about where your career goes next, understanding the strategic layer above project delivery is a meaningful differentiator, and it connects directly to the question of how to build a BA career strategy rather than drifting between assignments.
The most important shift in mindset for any BA or PM trying to make sense of portfolio management is to stop treating the constraints on your project as arbitrary interference and start reading them as strategic signals. Every time a budget is capped, a scope boundary is drawn, or a delivery date is immovable, there is a portfolio-level rationale behind it. The sooner you make it your business to find out what that rationale is, the more effective you will be at shaping requirements, managing stakeholders, and delivering something that the organisation actually values.
Frequently asked questions
What is project portfolio management in simple terms?
Project portfolio management is the process of selecting, prioritising, and governing a collection of projects to make sure the organisation invests in the right work at the right time. It sits above individual projects and ensures that all project activity is aligned to business strategy. Think of it as the mechanism that decides which projects get funded, which get paused, and which get cancelled.
What is the difference between project management and project portfolio management?
Project management focuses on delivering a specific scope within a defined timeline and budget. Project portfolio management focuses on the organisation’s entire body of project activity and makes decisions about where to invest resources for maximum strategic return. Portfolio management creates the context within which individual project managers operate.
How does project portfolio management affect business analysts?
Portfolio management decisions directly shape the scope, budget, and integration boundaries that business analysts work within on individual projects. When a BA receives a brief, the strategic rationale and investment limits have usually already been set at the portfolio level through an approved business case. Understanding this helps BAs ask better questions at kick-off and avoid eliciting requirements for scope that the organisation has already decided not to fund.
What does a project portfolio manager do?
A portfolio manager oversees the selection and governance of multiple projects and programmes, ensuring they are aligned to strategic objectives and delivered within the organisation’s resource capacity. They work with senior leadership and investment committees to prioritise competing project proposals and resolve resource conflicts across the portfolio. They also maintain oversight of benefits realisation to ensure that completed projects delivered what was promised.
Why do projects get cancelled or paused mid-delivery?
Projects are most commonly paused or cancelled because a portfolio governance body has decided that another project represents a better use of the available resources, or because the strategic rationale for the project has changed. This is a normal function of project portfolio management, not a sign of project failure. BAs and PMs who understand portfolio governance are better positioned to anticipate these decisions and frame their project’s value in terms that portfolio decision-makers respond to.
Try Ash, Your Virtual BA
If reading about project portfolio management has made you realise you want to sharpen the strategic layer of your BA practice, Ash can help you work through the concepts, terminology, and tools that connect portfolio thinking to day-to-day BA work. Whether you want to understand how a business case maps to a requirements scope, or you need to get up to speed on governance frameworks quickly, Ash gives you answers grounded in real BA practice rather than textbook definitions. Try Ash Virtual BA and get the strategic clarity your current project needs.
Further reading
Written by Sam Cordes, founder of the Business Analyst’s Toolkit.