Project Monitoring & Control - KU-SKE17/Software-Process GitHub Wiki

Goal

  • Compare Plan and Actual Work
  • If deviates significantly, then start the Corrective Actions

Note.

  • Plan/WBS: Product, Task Attributes, Effort, Cost, Schedule
  • Significant: What important for the project, depend on company/project objective [Quality, Time, Collaborative, ...]

PMC1 Monitor the Project Against the Plan

PMC1.1 Monitor Project Planning Parameters

  • Monitor progress against the schedule
  • Monitor the project’s costs and effort
  • Monitor the attributes of work products and tasks
  • Monitor resources provided and used
  • Monitor the knowledge and skills of staff
  • Document significant deviations

Output -> Significant Deviations

PMC1.2 Monitor Commitments

  • Regularly review commitments
  • Identify commitments that
    • have not been satisfied
    • are at significant risk of not being satisfied
  • Document the results of commitment reviews

Output -> Commitment Evident

PMC1.3 Monitor Project Risks

  • Periodically review the documentation of risks in the context of the project’s current status and circumstances
  • Revise the documentation of risks as additional information becomes available
  • Communicate the risk status to relevant stakeholders

Output -> Periodically Risk Analysis

PMC1.4 Monitor Data Management

  • Periodically review data management activities against their description in the project plan
  • Identify and document significant issues and their impacts
  • Document results of data management activity reviews

Output -> Periodically Data Management Review

PMC1.5 Monitor Stakeholder Involvement

  • Periodically review the status of stakeholder involvement
  • Identify and document significant issues and their impacts
  • Document the results of stakeholder involvement status reviews

Output -> Records of Stakeholder Involvement

PMC1.6 Conduct Progress Reviews

  • Regularly communicate status to stakeholders
  • Identify and document significant issues from the plan
  • Document change requests

Output -> Records of Review Results

PMC1.7 Conduct Milestone Reviews

  • Conduct milestone reviews at meaningful points in the schedule
  • Review commitments, the plan, status, and risks of the project
  • Identify and document significant issues, their impacts and action items

Note. Milestone and its schedule should be well known by anyone

Output -> Records of Milestone Review

PMC2 Manage Corrective Action to Closure

  • To solve Significant Deviations

PMC2.1 Analyze Issues

  • Gather issues for analysis
  • Analyze issues to determine the need for corrective action

Output -> List of Issues Requiring Corrective Actions

PMC2.2 Take CorrectiveAction

  • Example:
    • Modifying the statement of work (plan to do next)
    • Modifying requirements
    • Revising estimates and plans
    • Renegotiating commitments (tell worker to work short for his next task)
    • Adding resources (add workers)
    • Changing processes (change tasks dependency)
    • Revising project risk

Output -> Take Corrective Action