Getting scope and requirements right — and prioritising ruthlessly — is what keeps a project deliverable. This guide covers defining, prioritising and scheduling the work.
Defining scope
Scope is everything the project will (and won't) deliver. A clear scope statement lists deliverables, boundaries and exclusions. Its enemy is scope creep — uncontrolled additions that quietly blow the budget and timeline. The fix isn't saying no to everything; it's a change-control process so every addition is assessed against time, cost and quality before it's accepted.
Gathering requirements
Requirements describe what stakeholders need. Elicit them through interviews, workshops and observation; write them clearly (in agile, as user stories: "As a … I want … so that …"); and confirm them with stakeholders. Ambiguous requirements are the root of most delivery pain.
The Work Breakdown Structure (WBS)
Break the total scope into a hierarchy of smaller, manageable work packages. A good WBS makes estimating, assigning and tracking far easier — you can't schedule what you haven't decomposed.
MoSCoW prioritisation
You rarely have time for everything, so prioritise requirements with MoSCoW:
- Must have — non-negotiable; the project fails without it.
- Should have — important but not vital; painful to omit.
- Could have — desirable; include if time allows.
- Won't have (this time) — explicitly out of scope for now. MoSCoW protects the core outcome and gives you a principled way to flex scope under pressure — a favourite interview and assessment-centre technique.
Scheduling basics
- Gantt chart — tasks on a timeline showing durations and overlaps.
- Dependencies — which tasks must finish before others start.
- Critical path — the longest chain of dependent tasks; it determines the shortest possible project duration. Delays on the critical path delay the whole project.
- Milestones — key checkpoints with no duration, used to track progress.
Put it to work
Take a current piece of work, write a short scope statement, break it into a WBS, prioritise with MoSCoW, and identify the critical path. Practise prioritisation live in the Practical activities.