Wednesday, May 2, 2007

Project Monitoring and Control: Specifc Practices By Goal SG1

SG 1 Monitor Project Against Plan
Actual performance and progress of the project are monitored against the project plan.

SP 1.1 Monitor Project Planning Parameters
Monitor the actual values of the project planning parameters against the project plan. Project planning parameters constitute typical indicators of project progress and performance and include attributes of work products and tasks, cost, effort, and schedule. Attributes of the work products and tasks include such items as size, complexity, weight, form, fit, or function. Monitoring typically involves measuring the actual values of project planning parameters, comparing actual values to the estimates in the plan, and identifying significant deviations. Recording actual values ofthe project planning parameters includes recording associated contextual information to help understand the measures. An analysis of the impact that significant deviations have on determining what corrective actions to take is handled in the second specific goal and its specific practices in this process area.

Typical Work Products
1. Records of project performance
2. Records of significant deviations

Subpractices
1. Monitor progress against the schedule.
Progress monitoring typically includes the following:
· Periodically measuring the actual completion of activities and milestones
· Comparing actual completion of activities and milestones against the schedule documented in the project plan
· Identifying significant deviations from the schedule estimates in the project plan

2. Monitor the project's cost and expended effort.
Effort and cost monitoring typically includes the following:
· Periodically measuring the actual effort and cost expended and staff assigned
· Comparing actual effort, costs, staffing, and training to the estimates and budgetsdocumented in the project plan
· Identifying significant deviations from the budgets in the project plan

3. Monitor the attributes of the work products and tasks.Monitoring the attributes of the work products and tasks typically includes thefollowing:
· Periodically measuring the actual attributes of the work products and tasks, such as size or complexity (and the changes to the attributes)
· Comparing the actual attributes of the work products and tasks (and the changesto the attributes) to the estimates documented in the project plan
· Identifying significant deviations from the estimates in the project plan

4. Monitor resources provided and used.

For Software Engineering
Examples of software-engineering resources include the following:
· Host computers and peripherals
· Networks
· Software test computers and peripherals
· Target computer environment software
· Software-engineering environment (e.g., software tools)


SP 1.2 Monitor Commitments
Monitor commitments against those identified in the project plan.

Typical Work Products
1. Records of commitment reviews

Subpractices
1. Regularly review commitments (both external and internal).
2. Identify commitments that have not been satisfied or which are atsignificant risk of not being satisfied.
3. Document the results of the commitment reviews.

SP 1.3 Monitor Project Risks
Monitor risks against those identified in the project plan.

Typical Work Products
1. Records of project risk monitoring

Subpractices
1. Periodically review the documentation of the risks in the context ofthe project’s current status and circumstances.
2. Revise the documentation of the risks, as additional informationbecomes available, to incorporate changes. 3. Communicate risk status to relevant stakeholders.

Examples of risk status include the following:
· A change in the probability that the risk occurs
· A change in risk priority

SP 1.4 Monitor Data Management
Monitor the management of project data against the project plan.Once the plans for the management of project data are made, themanagement of that data must be monitored to ensure that those plans are accomplished.

Typical Work Products
1. Records of data management

Subpractices
1. Periodically review data management activities against theirdescription in the project plan.

2. Identify and document significant issues and their impacts.

3. Document the results of data management activity reviews.

SP 1.5 Monitor Stakeholder Involvement
Monitor stakeholder involvement against the project plan.
Once the stakeholders are identified and the extent of their involvementwithin the project is specified in project planning, that involvement mustbe monitored to ensure that the appropriate interactions are occurring.

Typical Work Products
1. Records of stakeholder involvement

Subpractices
1. Periodically review the status of stakeholder involvement.
2. Identify and document significant issues and their impacts.
3. Document the results of the stakeholder involvement statusreviews.

SP 1.6 Conduct Progress Reviews
Periodically review the project's progress, performance, andissues. Progress reviews are reviews on the project to keep stakeholdersinformed. These project reviews can be informal reviews and may notbe specified explicitly in the project plans.

Examples of these reviews include the following:
· Reviews with staff
· Reviews with project engineers and support
· Reviews with management

For Supplier Sourcing
Examples of these reviews also include the following:
· Reviews with key suppliers

Typical Work Products
1. Documented project review results

Subpractices
1. Regularly communicate status on assigned activities and workproducts to relevant stakeholders. Managers, staff members, customers, end users, suppliers, and other relevantstakeholders within the organization are included in the reviews as appropriate.

2. Review the results of collecting and analyzing measures forcontrolling the project.

3. Identify and document significant issues and deviations from theplan.

4. Document change requests and problems identified in any of thework products and processes.

5. Document the results of the reviews.

6. Track change requests and problem reports to closure.

SP 1.7 Conduct Milestone Reviews
Review the accomplishments and results of the project at selectedproject milestones. Milestone reviews are planned during project planning and are typicallyformal reviews.

Typical Work Products
1. Documented milestone review results

Subpractices
1. Conduct reviews at meaningful points in the project's schedule,such as the completion of selected stages, with relevant stakeholders. Managers, staff members, customers, end users, suppliers, and other relevantstakeholders within the organization are included in the milestone reviews asappropriate.

2. Review the commitments, plan, status, and risks of the project.

3. Identify and document significant issues and their impacts.

4. Document the results of the review, action items, and decisions.

5. Track action items to closure.