Analyze Project Metrics

(Activity) for Tier: Product

PURPOSE

The purpose of this activity is to prepare project personnel for the Monthly Status Review meeting by collecting and analyzing project specific metrics and determining if any specific corrective actions are needed. Metrics need to be analyzed in accordance with each organizationally defined metric, finally the results of analysis should be documented so that the information can be examined as needed. Decisions based on the results of collecting and analyzing data increase projects’ health and performance efforts.

PARTICIPATING ROLES

• ACCOUNTABLE

  • Project Lead

• RESPONSIBLE

  • Project Lead
  • Project Manager
  • Scrum Master
  • Development Manager

INPUTS

• Project Noncompliance Dashboard
• Project Sprint Burndown Chart
• Project Historical Velocity Bar Chart
• Project Scrum Quality Dashboard
• Project Risks
• Project Issues
• Vulnerability Score
• Pull Request Completion Status
• Code Review Quality Analysis for a Release

ENTRY CRITERIA

• Project Data has been collected and stored per each organizationally defined metric.

WHEN

Monthly or as requested by the executive team.

SUB-ACTIVITIES

1. Review Metric Definitions

   • Review the analysis method section of each of the input metrics definitions to ensure that analysis is performed in accordance to the metric definition. If additional analysis is desired take note so that this information can be provided as potential process improvement.

     Note

     It is important to understand each metric definition. Ensure that each metric is understood before moving into the analysis of specific data.

2. Perform Analysis on Project Metrics

   • Examine the input metrics for each applicable project. Use the analysis method within the appropriate metric definition to perform analysis. Identify potential areas of improvement by analyzing performance shortfalls or achievement excellence. Document the results of analysis and any perceived actions within the Project Reviews Notebook within OneNote.

     Note

     Projects may identify additional metrics to be presented to the executive team. When this is desired, a metric definition must be created and provided so that the metric can be reviewed, understood and approved for use. Refer to Manage Measurement and Analysis for more information.

3. Review Project Issues, Risks and Opportunities

   • Review escalated issues, risks and opportunities to ensure that any executive team support required is on track. Where needed take note of additional support within the discussion field of the appropriate risk or issue work item. Consider creating risks or issues for any new items identified and not yet documented. Refer to Plan for Risk and Opportunities for more information.

4. Prepare for Monthly Status Review

   • Share Azure DevOps project dashboard containing actual project metrics for Sprint Burndown chart and Historical Velocity to the Chief Technology Officer and Chief Operations Officer.
   • Invite additional project personnel as appropriate to support each measurement discussion. Be prepared to share analysis results and actions.
   • Complete any assigned action item(s) from the previous Monthly Status Review meeting.

OUTPUTS

• Project Metrics Analysis Results

EXIT CRITERIA

• Project measures have been analyzed per the analysis method of each organizational metric definition, and analysis results for each has been documented within the Project Reviews Notebook.

NEXT ACTIVITY

• Conduct Monthly Status Review

SEE ALSO

Process Guidance Version: 10.4