Skip to content
Tutorials Center
My learning

Topics

Lesson 9 of 41 ยท Initiation and Planning

The Project Plan: How to Make One

Learn what a project plan contains and how to build one step by step: objectives, scope, schedule, budget, resources, risks and communication, plus baselines and plan review.

A project plan is the document, or set of documents, that says how the project will be executed, monitored and controlled. The charter answers why and who; the plan answers what, when, how much, with whom and how we will keep it on track. A good plan is a working tool that people read and update, not a binder written once and filed.

Planning is progressive

You rarely know everything at the start. Plan in detail for the near term and at a higher level for the far future, then refine as facts arrive. This is called rolling-wave planning. Predictive projects plan more up front; adaptive projects plan each iteration in detail and keep a lightweight roadmap for the rest.

What a project plan contains

Component Question it answers Covered in
Objectives and success criteria What counts as success? Business case and charter
Scope statement and WBS What is in and out? What are the work packages? Scope management, WBS
Schedule When will each piece be done? Network diagrams, Critical path
Budget What will it cost? Cost estimation
Resource plan Who and what do we need? Activities and resources
Quality plan How do we make sure it is fit for use? Later chapter
Risk plan What could go wrong? Later chapter
Communication plan Who needs which information, how and when? Later chapter
Change control How are changes requested and approved? Below
Procurement plan What do we buy and from whom? Below

Step by step

  1. Confirm the objectives with the sponsor. Re-read the charter.
  2. Define the scope in writing, including what is excluded.
  3. Break the scope into work using a work breakdown structure.
  4. List the activities needed for each work package and their dependencies.
  5. Estimate effort, duration and cost.
  6. Build the schedule and find the critical path.
  7. Assign resources and check workloads.
  8. Plan quality, risk, communication and procurement.
  9. Set the baselines (scope, schedule, cost) as the approved reference.
  10. Review and get approval from the sponsor and key stakeholders.
flowchart TB
    A[Objectives] --> B[Scope and WBS]
    B --> C[Activities and estimates]
    C --> D[Schedule and critical path]
    D --> E[Resources and budget]
    E --> F[Quality, risk, communication]
    F --> G[Baselines]
    G --> H{Approved?}
    H -- No --> B
    H -- Yes --> I[Execute and control]

Planning loops until the sponsor approves; the approved plan becomes the baseline.

Baselines

A baseline is the approved version of a plan element that you measure against. The three common ones are the scope baseline, the schedule baseline and the cost baseline; together they form the performance measurement baseline. When work drifts from the baseline you will see it as a variance. Baselines change only through formal change control, never by quietly editing numbers.

Change control

Change will come. The plan should say how changes are handled:

  1. Someone submits a change request describing the change and why.
  2. The project manager analyzes the effect on scope, time, cost, quality and risk.
  3. The change control board (or sponsor) approves, rejects or defers.
  4. If approved, the plan and baselines are updated and everyone is told.

Small changes can have delegated approval limits so the team is not slowed down.

Assumptions, constraints and dependencies

Record these explicitly:

  • Assumptions: things believed true but unproven ("the vendor will deliver servers in March"). Each one is a latent risk.
  • Constraints: limits you cannot change (fixed launch date, budget cap, legal requirement).
  • Dependencies: things that must happen first, inside or outside the project.

A plan skeleton in code

Planning documents can be checked for completeness. This simple script verifies that no component is missing.

Python Plan completeness check

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Variance against the baseline

Python Compare plan and actual

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Good plans

  • Are as short as they can be and still useful.
  • Are owned by the team, not written by the manager alone. People commit to estimates they gave themselves.
  • Are version controlled and dated.
  • Include contingency for known uncertainty, and a management reserve for unknowns.
  • Are reviewed at every gate and whenever a major change occurs.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is a baseline?

    Baselines are approved references changed only through change control.
  2. 2. What is rolling-wave planning?

    You plan near work in detail and refine later work as information arrives.
  3. 3. Which is an assumption?

    An assumption is believed true but not proven; the others are constraints or dependencies.
  4. 4. After a change is approved, what must happen?

    The plan must reflect the approved change so everyone works to the same version.

Summary

  • The project plan describes how the project will be executed, monitored and controlled.
  • Components include scope, schedule, budget, resources, quality, risk, communication and change control.
  • Approved baselines are the yardstick for variance; change them only through change control.
  • Record assumptions, constraints and dependencies, and keep the plan alive.

Next: SDLC and the Waterfall Model