4.2 Develop Project Management Plan
Pull every area's plan into one document everyone works from.
Planning / Integration · ← PMBOK reference · See it on the map
Why it matters
A schedule that disagrees with the budget, or a risk plan nobody on the team has read, causes rework later that a single shared plan would have caught early.
What done looks like
Every knowledge area's plan is written down in one place and the team has it.
First time tip
Write it as a living document, not a binder for the shelf. Revisit it whenever a change is approved so it never goes stale.
What you need (Inputs)
How you do it (Tools & Techniques)
What you get (Outputs)
Worked example
For the library renovation, the project manager pulls the scope statement, the contractor's schedule, the materials budget and the safety plan into one shared document, so the electrician's outage window and the painter's drying time are visible on the same timeline instead of living in two separate emails.
Common pitfalls
- Writing the plan once and never updating it as scope or schedule changes get approved.
- Letting each area's plan live in its own file, so nobody notices when two disagree.
- Making the plan so detailed it takes longer to read than the work it describes.
How driftless helps
- Meetings can be run here.