Showing posts with label Project management process. Show all posts
Showing posts with label Project management process. Show all posts

Monday, November 8, 2010

Project Monitoring and Control (PMC)

Project Monitoring and Control (PMC) is a Project Management Process Area at Maturity Level 2.

The purpose of Project Monitoring and Control is to provide an visualization of the project’s progress so that appropriate corrective actions can be taken when the project’s performance deviates significantly from the plan.

Monitoring activities, communication status, and corrective actions are based on project plan. The project progress is primarily determined by comparing actual work products and task attributes, cost, effort and schedule to the plan at each milestones within the project schedule or work breakdown structure (WBS). Timely corrective actions is taken according to appropriate visibility of significantly deviations between project performance and plan. A deviation is significant if, when left unresolved, it precludes the project from meeting its objectives.


The term “project plan” is used to refer to the overall plan for controlling the project
.

When actual status deviates significantly from the expected values, corrective actions are taken as appropriate. These actions may require re-planning, which may include revising the original plan, establishing new agreements, or including additional mitigation activities within the current plan.


To understand more about this process area:


- Refer to the Project Planning process area for more information about the project plan, including how it specifies the appropriate level of project monitoring, the measures used to monitor progress, and known risks.


- Refer to the Measurement and Analysis process area for information about the process of measuring, analyzing, and recording information.

Specific Goal and Practice Summary for this process area:

SG 1 Monitor Project Against Plan

  • SP 1.1 Monitor Project Planning Parameters
  • SP 1.2 Monitor Commitments
  • SP 1.3 Monitor Project Risks
  • SP 1.4 Monitor Data Management
  • SP 1.5 Monitor Stakeholder Involvement
  • SP 1.6 Conduct Progress Reviews
  • SP 1.7 Conduct Milestone Reviews
SG 2 Manage Corrective Action to Closure
  • SP 2.1 Analyze Issues
  • SP 2.2 Take Corrective Action
  • SP 2.3 Manage Corrective Action

Sunday, November 7, 2010

Project Planning

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 Summar
y for Project Planning process area
SG 1 Establish Estimates
  • 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
SG 2 Develop a Project Plan
  • 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
SG 3 Obtain Commitment to the Plan
  • SP 3.1 Review Plans That Affect the Project
  • SP 3.2 Reconcile Work and Resource Levels
  • SP 3.3 Obtain Plan Commitment