Monitor the Project Against the Plan

Purpose:

<?>

Objective:

Actual project progress and performance are monitored against the project plan.

Description:

Monitoring acquirer project progress and performance begins as soon as a plan is established. The acquirer is responsible for monitoring the progress and output of the project. After a supplier is selected and a supplier agreement is put in place, the acquirer’s monitoring and control activities extend to the supplier and its activities. The acquirer monitors supplier progress, including achieving requirements established in the supplier agreement and using specified processes, products, and service level measures.

Inputs:

<?>

Outputs:

<?>

Controls:

<?>

Task Instructions:

Monitor Project Planning Parameters

1. 1. Using the <?>, [the ?] with support from <?> is responsible for monitoring progress against the schedule. 
   2. Using the <?>, [the ?] with support from <?> is responsible for monitoring the project’s costs and expended effort.
   3. Using the <?>, [the ?] with support from <?> is responsible for monitoring the attributes of work products and tasks. 
   4. Using the <?>, [the ?] with support from <?> is responsible for monitoring resources provided and used. 
   5. Using the <?>, [the ?] with support from <?> is responsible for monitoring the knowledge and skills of project staff.
   6. Using the <?>, [the ?] with support from <?> is responsible for documenting significant deviations in project planning parameters.

Monitor Commitments

1. 1. Using the <?>, [the ?] with support from <?> is responsible for regularly reviewing commitments (both external and internal).
   2. Using the <?>, [the ?] with support from <?> is responsible for identifying commitments that have not been satisfied or are at significant
      risk of not being satisfied.
   3. Using the <?>, [the ?] with support from <?> is responsible for documenting the results of commitment reviews.

Monitor Project Risks

1. 1. Using the <?>, [the ?] with support from <?> is responsible for periodically reviewing the documentation of risks in the context of the project’s current status and circumstances.
   2. Using the <?>, [the ?] with support from <?> is responsible for revising the documentation of risks as additional information becomes available. 
   3. Using the <?>, [the ?] with support from <?> is responsible for communicating the risk status to relevant stakeholders.

Monitor Data Management

1. 1. Using the <?>, [the ?] with support from <?> is responsible for periodically reviewing data management activities against their description in the project plan.
   2. Using the <?>, [the ?] with support from <?> is responsible for identifying and documenting significant issues and their impacts. 
   3. Using the <?>, [the ?] with support from <?> is responsible for documenting the results of data management activity reviews.

Monitor Stakeholder Involvement

1. 1. Using the <?>, [the ?] with support from <?> is responsible for periodically reviewing the status of stakeholder involvement.
   2. Using the <?>, [the ?] with support from <?> is responsible for identifying and documenting significant issues and their impacts.
   3. Using the <?>, [the ?] with support from <?> is responsible for documenting the results of stakeholder involvement status reviews.

Conduct Progress Reviews

1. 1. Using the <?>, [the ?] with support from <?> is responsible for regularly communicating the status of assigned activities and work products to relevant stakeholders.
   2. Using the <?>, [the ?] with support from <?> is responsible for reviewing the results of collecting and analyzing measures for controlling the project.
   3. Using the <?>, [the ?] with support from <?> is responsible for identifying and documenting significant issues and deviations from the plan.
   4. Using the <?>, [the ?] with support from <?> is responsible for documenting change requests and problems identified in work products and processes.
   5. Using the <?>, [the ?] with support from <?> is responsible for documenting the results of reviews.
   6. Using the <?>, [the ?] with support from <?> is responsible for tracking change requests and problem reports to closure.

Conduct Milestone Reviews

1. 1. Using the <?>, [the ?] with support from <?> is responsible for conducting milestone reviews with relevant stakeholders at meaningful points in the project’s schedule, such as the completion of selected phases.
   2. Using the <?>, [the ?] with support from <?> is responsible for reviewing commitments, the plan, status, and risks of the project.
   3. Using the <?>, [the ?] with support from <?> is responsible for identifying and documenting significant issues and their impacts.
   4. Using the <?>, [the ?] with support from <?> is responsible for documenting the results of the review, action items, and decisions.
   5. Using the <?>, [the ?] with support from <?> is responsible for tracking action items to closure.

Monitor Transition to Operations and Support

1. 1. Using the <?>, [the ?] with support from <?> is responsible for monitoring the operations and supporting the organization’s capability and facilities designated to receive, store, use, and maintain acquired products.
   2. Using the <?>, [the ?] with support from <?> is responsible for monitoring the delivery of training for those who are involved in receiving, storing, using, and maintaining acquired products.
   3. Using the <?>, [the ?] with support from <?> is responsible for reviewing pilot results, if any, and operational readiness reports for the acquired product. 
   4. Using the <?>, [the ?] with support from <?> is responsible for reviewing and analyzing the results of transition activities.