Summary

Collect and analyze issues and determine corrective actions to address them.

Description

This analysis is performed for a different purpose and generally on different issues than the analysis performed as part of incident analysis, or change request analysis. However, the same or a similar mechanism can be used to analyze each of these types of issues and to manage them to closure. How best to implement a common solution for their analysis and management to closure depends on the risk of failing to handle each appropriately and the costs incurred by alternative solutions.

Example Work Products



  1. List of issues requiring corrective actions


Subpractices



1. Gather issues for analysis.

Issues are collected from reviews and the execution of other processes.

 

Examples of issues to be gathered include the following:
  • Issues discovered when performing verification and validation
  • Significant deviations in planning parameters from estimates in the work plan
  • Commitments (either internal or external) that have not been satisfied
  • Significant changes in risk status
  • Data access, collection, privacy, or security issues
  • Stakeholder representation or involvement issues
  • Product, tool, or environment transition assumptions (or other customer or supplier commitments) that have not been achieved



2. Analyze issues to determine the need for corrective action.

Refer to the Establish the Budget and Schedule specific practice in the Work Planning (WP) (CMMI-SVC) process area for more information about corrective action criteria.


Corrective action is required when the issue, if left unresolved, may prevent the work from meeting its objectives.