Practice: Project Planning (PP)
The purpose of Project Planning (PP) is to establish and maintain plans that define project activities.
Relationships
Goals

The following specific goals are associated with this process area:

SG 1 Establish Estimates

Estimates of project planning parameters are established and maintained.

Project planning parameters include all information needed by the project to perform the necessary planning, organizing, staffing, directing, coordinating, reporting, and budgeting.

Estimates of planning parameters should have a sound basis to instill confidence that any plans based on these estimates are capable of supporting project objectives.

Factors that are typically considered when estimating these parameters include the following:

  • Project requirements, including the product requirements, the requirements imposed by the organization, the requirements imposed by the customer, and other requirements that impact the project
  • Scope of the project
  • Identified tasks and work products
  • Technical approach
  • Selected project lifecycle model (e.g., waterfall, incremental, or spiral)
  • Attributes of the work products and tasks (e.g., size or complexity)
  • Schedule
  • Models or historical data for converting the attributes of the work products and tasks into labor hours and cost
  • Methodology (e.g., models, data, algorithms) used to determine needed material, skills, labor hours, and cost

Documentation of the estimating rationale and supporting data is needed for stakeholders’ review and commitment to the plan and for maintenance of the plan as the project progresses.

SG 2 Develop a Project Plan

A project plan is established and maintained as the basis for managing the project.

A project plan is a formal, approved document used to manage and control the execution of the project. It is based on the project requirements and the established estimates.

The project plan should consider all phases of the project lifecycle. Project planning should ensure that all plans affecting the project are consistent with the overall project plan.

SG 3 Obtain Commitment to the Plan

Commitments to the project plan are established and maintained.

To be effective, plans require commitment by those responsible for implementing and supporting the plan.

Main Description

The Project Planning process area involves the following:

  • Developing the project plan
  • Interacting with stakeholders appropriately
  • Getting commitment to the plan
  • Maintaining the plan

Planning begins with requirements that define the product and project.

Planning includes estimating the attributes of the work products and tasks, determining the resources needed, negotiating commitments, producing a schedule, and identifying and analyzing project risks. Iterating through these activities may be necessary to establish the project plan. The project plan provides the basis for performing and controlling the project’s activities that address the commitments with the project’s customer.

The project plan will usually need to be revised as the project progresses to address changes in requirements and commitments, inaccurate estimates, corrective actions, and process changes. Specific practices describing both planning and replanning are contained in this process area.

The term “project plan” is used throughout the generic and specific practices in this process area to refer to the overall plan for controlling the project.

Additional Information

Refer to the  Requirements Development (RD) process area for more information about developing requirements that define the product and product components. Product and product component requirements and changes to those requirements serve as a basis for planning and replanning.

Refer to the  Requirements Management (REQM) process area for more information about managing requirements needed for planning and replanning.

Refer to the Risk Management (RSKM) process area for more information about identifying and managing risks.

Refer to the  Technical Solution (TS) process area for more information about transforming requirements into product and product component solutions.