person Author: Process Fellows
Problem status reports are often generated automatically by Application Lifecycle Management (ALM) tools. These reports are produced on a regular basis to support consistent tracking and reporting of open issues. They serve as a basis for initiating corrective actions—especially when problem trends show no improvement over time.
Recommended use of reports: Reports should not only reflect the current status but also trigger action. For example, if the number of unresolved issues remains high or increases, this should prompt further analysis and corrective action.

Exemplary key metrics to monitor:

• Current problem status distribution: Number of problems per status (e.g., open, in progress, resolved, closed).
• Overdue and aging issues: Identification of problems that exceed their expected resolution time, including age analysis.
• Problem categorization: Source of problem reports (e.g., internal vs. customer-reported). Distribution by component or subsystem.
• Inflow vs. outflow trends: Number of new problems reported per calendar week. Number of problems resolved in the same period.
• Severity-based breakdown: Reports should differentiate by severity level. For instance, a backlog of minor issues may be acceptable, whereas unresolved critical or showstopper issues require immediate attention.