Reflecting on my top 5 modules: Programme, Portfolio and Project Management

If you've been following along, I'm doing a five-part series on the modules from my Level 6 Project Management Degree Apprenticeship at Northumbria University that actually changed how I work. Not a dry academic recap, just an honest reflection on what stuck, what didn't, and what I'd tell someone starting out.

This one is a bit different from the others, because it was the first module I ever did on the course.

And I had to re-sit it.

A baptism of fire

I came to this course straight from sixth form. No real experience in delivery, no idea what a business case was, and genuinely no frame of reference for most of the concepts being thrown at me. I sat down to write my first ever university assignment and produced something that, looking back, read more like a GCSE report than Level 6 academic work. All assertion, not much argument, and a fairly shaky grasp of what programme, portfolio and project management actually meant.

Re-sit it was.

The re-sit came back as a first. I'd like to say that was always the plan.

What the module actually covers

The nine weeks move through a lot of ground: project management fundamentals, programme and portfolio thinking, strategic context, the Programme Management Office, Managing Successful Programmes, defining and delivering capability, and closing things out properly.

The framing that took longest to click was the difference between the three levels. I assumed they were just different scales of the same thing. Bigger project equals programme. Even bigger equals portfolio. That's not it.

A project delivers a specific output. A programme coordinates a set of related projects to achieve an outcome you couldn't reach by running each project independently. A portfolio sits above all of that, selecting and balancing programmes and projects against organisational strategy and available resource. Three distinct conversations, three different sets of questions, and they all have to connect to each other.

That last bit is the one that matters.

The numbers that put it in perspective

Here's the thing that strikes me every time I look at the research on this. BCG's 2024 study of large-scale technology programmes found that more than two-thirds were not expected to be delivered on time, within budget and within scope. That's not a delivery problem in isolation. BCG ties poor outcomes directly to inaccurate timeline and resource planning, weak end-to-end roadmaps, and ineffective management of interdependencies, and frames it explicitly as a portfolio design problem, not just execution.

Organisations that excel at aligning projects with strategy are 50% more likely to finish on time and 45% more likely to stay on budget.

And yet. Only 18% of project professionals currently demonstrate high business acumen proficiency. The gap between knowing delivery and understanding the strategic context it sits in is still enormous across the profession.

I find that genuinely alarming. And I also find it quietly motivating.

What actually stuck

The thing that landed hardest was this: every project has a strategic context, and if you don't understand that context, you're just executing tasks.

The business case section made that concrete. Before this module, I thought a business case was admin. A document you filled in before the real work started, signed off by someone senior, filed somewhere and never looked at again. The module reframed it as the argument for why a particular bet is worth making. Resource is finite. Every project competes with other projects for time, money, and people. A business case is how an organisation decides what to back, and more importantly, what not to back.

That reframing changed how I approach the start of projects. I ask more questions now about why something exists, not just what it needs to deliver. What outcome sits behind this output? Who benefits if this works? What does the organisation lose if it doesn't happen, or if it happens badly?

Those feel like obvious questions. They're genuinely not, when you're under pressure to just get things moving.

What it looks like in practice

Working across financial services, healthcare and public sector, the projects look different on the surface. The underlying tension is the same across all of them: more potential work than there is resource or budget to do it. Decisions get made every day about what gets prioritised, what gets pushed, what gets stopped. That's portfolio thinking, whether anyone uses that word or not.

In a recent engagement, a client had three significant pieces of work all competing for the same internal resource. None of them were wrong to want doing. But without a clear view of which one served the most critical strategic objective, the default was to try and run all three at the same time, with predictable results. The conversation that helped wasn't about delivery capacity, it was about strategic priority. Which of these moves the needle most? Which one, if it slipped, would actually hurt?

That's a programme and portfolio management conversation. And I wouldn't have known how to have it without this module giving me the vocabulary and the framework first.

The PMI's 2025 Pulse of the Profession research is clear that project professionals need to go beyond managing scope, budget and schedule, becoming strategic partners who support organisational objectives. That direction of travel feels right to me. It's also where the interesting work is.

On the re-sit

I could gloss over this, but the whole point of this series is honest reflection.

I struggled with this module because I had no context. I hadn't worked in delivery long enough to have real examples to draw on. I'd never written a university essay. The first submission was vague where it needed to be specific, and confident where it should have been more careful. I didn't know enough to know what I didn't know.

The re-sit forced me to properly engage with the material. To read it again, think about it differently, and write about it with some actual substance rather than just restating the theory back at the examiner. That process of returning to something you half-understood and realising you'd only scratched the surface — that's a genuinely useful skill in itself. I've had that same experience on projects plenty of times since.

If you're starting a degree apprenticeship and your first module doesn't go the way you hoped, it's not the end. You probably just need a bit more time and context before it properly clicks. I certainly did.

Next up: Governance and Financial Control. The one that made me realise how much I didn't know about money.