Project Planning and Control
Plan a Baseline, Then Control Against Evidence
Planning begins by defining the deliverable, boundaries, acceptance criteria, stakeholders, assumptions, and constraints. A work breakdown structure decomposes the deliverable into manageable work packages with owners. Estimates and dependencies create a schedule baseline; planned cost and scope create companion baselines.
Control is not merely status reporting. At a regular cadence, compare actual progress, cost, and remaining work with the baseline; distinguish a measured variance from its cause; forecast the effect on the completion date or budget; then decide whether to correct work, re-plan through change control, or accept the risk.
A milestone is a zero-duration decision or achievement point, not a task disguised with a date.
Baselines should change only through documented authorization. Otherwise a team can make variance disappear on paper by repeatedly moving the target. A useful status report names the evidence date, the owner, the variance, its cause or uncertainty, the next decision, and the effect of doing nothing.
Which item is best written as a project milestone?
A work package is behind its planned finish date. What is the best first control response?