Project Plan

The document that lays out how your scope will get done: the phases, the deadlines, and who is responsible for what.

Where scope answers what and the project charter answers why, the project plan answers how and when. It sequences the work, assigns roles, and sets the milestones everyone will be measured against.

A good plan is honest about dependencies. For example, a good project plan is clear that content migration can't finish before the content model is built, and it doesn't pretend two things can happen at once when they can't.