Plans at the right level

What you will understand

• Distinguish project, stage, team and exception plans.
• Explain why detailed planning has a limited horizon.
• Recognise a work package as an agreement about delivery.

The idea

A detailed timetable for the distant future can look reassuring while resting on assumptions nobody can defend. A plan should provide enough information for a particular decision and management responsibility. Different levels of plan connect overall investment control to the practical products, resources and work that a team can commit to delivering.

The project plan provides the overall picture: major products, delivery timescales, costs, management stages and important control points. It supports the business case and helps the board assess project-level progress. It is not simply a collection of every task. Its estimates can be refined as the project learns more, with changes controlled against the authorised baseline.

A stage plan gives the project manager a sufficiently detailed basis for controlling one management stage. It identifies the products, resources, activities, costs and controls needed within that stage. At an approaching stage boundary, information from completed work supports a more credible plan for the next stage. Technical activities may overlap, but management stages provide successive decision periods rather than overlapping delegations of management authority.

A team plan, where useful, helps a team manager organise agreed delivery work. It may use a specialist scheduling format, a task board or another suitable arrangement. Its format matters less than whether it supports reliable delivery commitments and reporting. A work package description defines the agreed products and delivery arrangements between the project manager and the team manager; it is not simply another name for the team’s internal schedule.

An exception plan is prepared when requested by the appropriate directing authority after a forecast tolerance breach has been escalated. It offers a proposed replacement for the affected project or stage plan, covering the remaining work and consequences. Preparing a proposal does not authorise it. Once approved, the replacement becomes the basis for control. A team-level forecast breach is escalated to the project manager for action; it does not automatically require a board-approved exception plan.

The planning horizon is the distance into the future for which useful detail can be produced with reasonable confidence. Unfamiliar technology, volatile demand or uncertain approvals may shorten it. Keep a view of the whole project while detailing nearer work and refining later work when evidence improves. A plan includes assumptions, responsibilities, dependencies, risks, tolerances and controls as well as dates. Removing those explanations leaves a schedule that can conceal why its dates might fail.

Plans answer different levels of question

Points to remember

• An exception plan requires authorisation before replacing a baseline.
• A work package agreement and an internal team plan have different purposes.
• A planning horizon reflects uncertainty, not merely the project end date.

Your takeaway

Use project, stage and optional team plans at suitable levels of detail. An authorised exception plan replaces an affected baseline; a planning horizon helps decide where detailed forecasts are credible.