PLANNING – KEY INPUTS FOR DEVELOP SCHEDULE

The development of the program plan requires some key inputs;

• Project Charter (4.1)
• Project Scope (5.3)
• Work Breakdown Structure (5.4)

Project Charter (PMBOK 4.1)

The project charter documents the business need and high level requirements for the expected product, service or result.  The Charter contains key inputs for the program plan such as the summary milestone schedule and key constraints.

Project Scope (PMBOK 5.3)

The project scope defines the work which needs to be completed to deliver the product, service or result with the specified features or functions.   The scope of the project is defined at a high level in the Initiation phase and is further elaborated as the project progresses through feasibility phase in the Scope statement.  Changes to scope are managed via the change control process (5.6 Control Scope).

The project scope baseline is a key input to the development of the program plan. 

Any changes to the scope baseline must be reflected with an update to the program plan and potentially the Work Breakdown Structure.

Work Breakdown Structure (PMBOK 5.4)

The Work Breakdown Structure is a hierarchical decomposition of the total scope of the program which defines and organizes the scope of the program.  The WBS provides a program framework for project control, schedule management and effort estimation.

The Program Work Breakdown Structure is used by the Schedule Manager to define the Levels of activity in the program and project plans.  Since all scope of the project is included in the Work Breakdown Structure then clear accountability for scope delivery will be defined by the WBS.

One objective of the Schedule Manager is to ensure all scope elements are included in the program plan and any lack of clarity regarding scope accountability or delivery is clearly highlighted to the program management team.