Every discipline begins with its distinctions, and this one begins with the difference between a project and everything else an organisation does. You'll learn what gives project work its particular shape, who the players are, from the sponsor who commissions it to the stakeholders who feel its effects, and the four phases every project moves through between first idea and final handover. You leave able to look at any project and see its structure.

No project succeeds on its plan alone, because no project happens in a vacuum. This module teaches you to read the world around one: the strategy it's meant to serve, the culture and governance that will help or hinder it, and the people whose influence can smooth its path or quietly end it. You'll learn to map stakeholders and what each of them needs, and to understand how a project creates value an organisation can actually measure.

Here the craft begins in earnest. You take a project brief and turn it into something that can be run: a clear record of what's in and what's out, the work broken into manageable pieces, activities in a sensible sequence, and an honest estimate of the time, people and materials it will all require. These are the documents every project stands on, and you build them yourself.

Some projects can be planned in full before the work begins, and when they can, there is a right way to do it. You'll learn to build the structured, detailed plans used on everything from infrastructure to system rollouts: complete schedules, mapped dependencies, and the baselines that let you measure delivery against the promise. You'll also learn where this approach reaches its limits, which matters just as much.

Other projects refuse to hold still. Requirements evolve, feedback reshapes the picture, and a plan fixed in January is fiction by March. This module teaches the iterative way of working built for exactly those conditions: short cycles, work drawn from a continuously re-prioritised backlog, and progress delivered in usable increments. Then it shows you how predictive and agile combine into hybrid delivery, and how to choose the right approach for the project in front of you.

Every project meets trouble; the difference between a setback and a disaster is usually whether anyone saw it coming. You'll learn to search for risk systematically, record it, weigh its likelihood and impact, and decide your response before you need it. You'll also learn what to do once trouble has arrived, and how to take a change request through proper assessment so that mid-project changes never quietly double the work.

Much of project management is the management of people, most of whom don't report to you. This module covers what makes project teams perform, how to keep stakeholders engaged in proportion to their influence, and how to design project communication so that decisions, risks and changes reach the right people at the right time, in a form they will actually read.

Finishing well is a skill of its own. You'll learn to define what good looks like before anything is built, to check quality along the way rather than discover its absence at the end, to measure whether the project achieved what it was for, and to close it down properly: acceptance confirmed, handover complete, resources released, and the lessons recorded for the next one.

The final two weeks draw the whole course together. Working from a realistic project brief, you produce the document every well-run project begins with: a complete Project Management Plan. Its purpose and boundaries, a delivery approach chosen and justified, scope and milestones, risks and resources, stakeholders and communication, each element thought through and defensible.

It is both the proof of what you've learned and the first artefact of how you'll work from now on.