The M1: Iteration Metrics are based on the SAFE® Agile Metrics and are used to measure the iteration. The Iteration Metrics are broken into functionality and quality reports. Functionality reports determine metrics such as planned velocity versus actual velocity, as an example, and the quality reports are used to determine important quality indicators such as the number of tests cases and open defects. SAFE® metrics on Jira can be obtained through the below reports which have been developed on Jira by Infoware Studios

Functionality

The Functionality reports can be filtered on any of the below:

  • Any other date range
  • Portfolio (optional)
  • Programme (optional)
  • Project (optional)
  • PSI / Release boundaries (optional)
  • Sprints (optional)

The Functionality reports consist of the following:

  • Velocity planned / actual
  • No of stories planned / accepted (resolved, closed, or identify other status relevant)
  • Percentage (%) of stories accepted

For example:
Agile metrics on Jira: Velocity Chart

Quality

The Quality reports can be filtered on any of the below:

  • Sprint boundaries
  • Any other date range
  • PSI boundaries

The quality reports consist of the following:

  • Percentage (%) unit test coverage (Bamboo & Clover)
  • Open defects
  • Number of new test cases
  • Number of new test cases automated
  • Total number of tests
  • Total percentage (%) test automated
  • Number of refactors

For example:
Agile metrics on Jira: Stories vs Bugs

Agile metrics on Jira: Code coverage