Project planning is a Project Management Process Area at Maturity Level 2.
The purpose of Project Planning (PP) is to establish and maintain plans that define project activities.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 analysing 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 re-planning 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.
To make the best project plan:
- Refer to the Requirements Development 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 re-planning.
- Refer to the Requirements Management process area for more information about managing requirements needed for planning and re-planning.
- Refer to the Risk Management process area for more information about identifying and managing risks.
- Refer to the Technical Solution process area for more information about transforming requirements into product and product component solutions.
Specific Goal and Practice Summary for Project Planning process area
SG 1 Establish EstimatesThe 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 re-planning 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.
To make the best project plan:
- Refer to the Requirements Development 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 re-planning.
- Refer to the Requirements Management process area for more information about managing requirements needed for planning and re-planning.
- Refer to the Risk Management process area for more information about identifying and managing risks.
- Refer to the Technical Solution process area for more information about transforming requirements into product and product component solutions.
Specific Goal and Practice Summary for Project Planning process area
- SP 1.1 Estimate the Scope of the Project
- SP 1.2 Establish Estimates of Work Product and Task Attributes
- SP 1.3 Define Project Lifecycle
- SP 1.4 Determine Estimates of Effort and Cost
- SP 2.1 Establish the Budget and Schedule
- SP 2.2 Identify Project Risks
- SP 2.3 Plan for Data Management
- SP 2.4 Plan for Project Resources
- SP 2.5 Plan for Needed Knowledge and Skills
- SP 2.6 Plan Stakeholder Involvement
- SP 2.7 Establish the Project Plan
- SP 3.1 Review Plans That Affect the Project
- SP 3.2 Reconcile Work and Resource Levels
- SP 3.3 Obtain Plan Commitment
No comments:
Post a Comment