Planning is where the project stops being a speech and becomes a set of decisions that can be baselined. It is the largest process group because every knowledge area grows a plan, and those plans have to survive contact with one another. A folder of disconnected documents is a library, not a management system.
Planning is a web, not a waterfall of templates
You do not write the scope plan, then the schedule, then the cost plan as if each were a completed essay. Scope changes the work packages; work packages change duration; duration and resources change cost; risk changes all three. If your plans cannot refer to each other, one of them is already a lie.
The project management plan is the integrator: how you will execute, monitor, and control, plus the subsidiary plans for scope, schedule, cost, quality, resources, communications, risk, procurement, and stakeholder engagement. You do not need a novella for each. You need enough that a stranger could see how a change in one place ripples.
Progressive elaboration is not an excuse for vagueness. Early plans are rightly coarse. They still need owners, assumptions, and a date when the next level of detail is due. 'We will figure it out in execution' is how planning becomes a kickoff slide.
Baselines are why you bothered
When planning is good enough, you freeze scope, schedule, and cost as the performance measurement baseline. That freeze is a decision, not a mood. After it, deviation is a change or a variance — not a quiet edit to the spreadsheet so the line still looks straight.
Get the people who will be measured against the baseline to help build it. A schedule the team never saw is a hostage note. A budget finance never recognised is a wish. Sign-off is not ceremony; it is how you later say 'this is what we agreed' without sounding like you invented it yesterday.
Watch the assumption log. Plans fail less from missing tasks than from 'the vendor environment will be ready in June' sitting untested until June. If an assumption would change the baseline if it were false, it needs an owner and a check date. Hope is not a subsidiary plan.
Enough planning is a judgement, not a page count
Under-planning shows up as firefighting and surprise dependencies. Over-planning shows up as a team that cannot start because the document set is still 'in review.' Your job is to judge which constraint is currently the dangerous one — usually the one nobody wants to name.
Tailor. A six-week internal tool does not need the same planning stack as a regulated multi-vendor programme. Using every process because a diagram showed them all is cargo-cult PMBOK. Skipping integration because you are 'agile now' is how hybrids invent two baselines that disagree.
Planning does not end when execution starts. You re-plan when authorised change lands, when a phase starts, and when reality makes the current baseline dishonest. Treating the plan as a relic is how monitoring becomes archaeology.
Summary & next steps
Planning connects subsidiary plans through an integrated project management plan, then freezes a baseline you can measure. Elaborate as you learn; do not confuse a template pile with a plan. Tailor the stack to the risk, not the diagram.
Next: Executing processes — directing the work, managing the team, and resisting the urge to call activity a result.