Key Takeaways
- ✓ A Project Management Plan is the central governance document recording the agreed scope, SMART objectives, deliverables, quality standards, risk management approach and communication plan; it is the baseline against which project performance is monitored throughout the lifecycle.
- ✓ Scope creep is the gradual expansion of project scope beyond the original agreement without corresponding increases in time or budget; a clearly defined scope statement with explicit exclusions is the most effective preventive tool.
- ✓ A project risk register records each identified risk, its probability, impact, owner and planned mitigation and contingency responses; it is a live document updated continuously throughout the project as new risks emerge and planned responses are tested.
Full Transcript
What should a project management plan include?
Alex: Welcome to the Leadership and Management podcast. I'm Alex, joined by Sam. Last time we laid the groundwork for project management: the lifecycle, the methodologies. Today we're getting into what sits at the centre of any well-run project: the Project Management Plan.
Sam: The PMP. And I'll say it plainly: a project without a plan is a project waiting to fail. The PMP is the single document that defines what you're going to do, how you're going to do it, who's involved, what resources you need, what risks you face, and how you'll communicate progress.
How do you define scope, objectives and deliverables for a project?
Alex: Let's start where every PMP starts: scope. Because defining what the project is and isn't is more difficult than it sounds.
Sam: Scoping is genuinely challenging. A well-scoped project has clear boundaries. A poorly scoped project suffers from scope creep, which is one of the top five causes of project failure according to the Project Management Institute. Scope creep is where the project gradually expands beyond its original boundaries, usually because stakeholders keep adding requirements. Your aim is a single, overarching statement of what the project intends to achieve. Your objectives are the measurable steps that will get you there, and they should be SMART: specific, measurable, achievable, relevant, and time-bound.
Alex: A SMART objective in practice. Can you give an example of a weak one being improved?
What is scope creep and how can project managers prevent it?
Sam: Of course. A weak objective might be: 'Improve staff satisfaction.' It sounds like a reasonable aim, but there's no measurement, no timescale, no clear benchmark. A SMART version would be: 'Increase the employee satisfaction score, as measured by the annual staff survey, from 62% to 75% by the end of Q3 of this financial year, through the implementation of a flexible working pilot for the customer services team.' Now you have something you can actually manage against and assess at the end.
Alex: The resource plan and research approach round out the seven components.
Sam: Resources covers everything: who is working on the project and what time they're committing, what equipment or technology is needed, what budget is available. And for any project that involves investigation or evidence-gathering, the research approach defines what data you need, how you'll collect it, and why you've chosen those methods over alternatives. That last part, the justification, is what separates a plan that describes what you're doing from one that demonstrates you've thought through why.
How do you write a SMART objective for a project?
Alex: And that 'why' is what separates a competent plan from an excellent one.
Sam: Always. Description tells examiners, managers, and sponsors what exists. Justification tells them why it was designed that way, which demonstrates genuine understanding and professional judgement.
Why does a project plan need both a description and a justification?
Alex: Here's a thought: consider a project, current or past, that you know something about. If you had to write a one-page PMP for it today, which of the seven components would be easiest and which would force you to think hardest? What does that tell you about where the real complexity lies?