Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Next »

KPI Name / Definition

Representation

Tool

Maturity Level

Filters

KPI Calculation

On Hover

Remarks

Release progress KPI explains the count of issues in To-Do, In Progress, Done.

Horizontal Percent Bar Chart

  • It gives the breakup (To-do, In Progress, Done) based on size (story points)

Agile Project Management

  • Jira

  • Azure Boards

No Maturity

  • Filter By Assigne

  • Filter Ny Priority

It is calculated as a ‘Percentage’ for To, In Progress, Done based on size i.e story Point

Story Point: <<Percentage Value>>

Issue Count: <<Percentage Value>>

Defect count by Status

It shows the breakup of all defects within an iteration by Status.

Pie Chart

  • Slices represent the count of defects in each Status

Agile Project Management

  • Jira

  • Azure Boards

No Maturity

No Filter

the size of each slice would correspond to the proportion of data points belonging to that particular status

No Effect

Defects are considered based on the field ‘Issue type to identify defect’ which falls under Jira/Azure Mappings--> Defect Mappings

Defect count by RCA

It shows the breakup of all defects within an iteration by status.

Pie Chart

  • the count of defects in each RCA

Agile Project Management

  • Jira

  • Azure Boards

No Maturity

No Filter

the size of each slice would correspond to the proportion of data points belonging to that particular RCA

No Effect

Defects are considered based on the field ‘Issue type to identify defect’ which falls under Jira/Azure Mappings--> Defect Mappings

Defect Count by Priority

It shows the breakup of all defects within an iteration by Priority.

Pie Chart

  • Slices represent count of defects in each Priority

Agile Project Management

  • Jira

  • Azure Boards

No Maturity

No Filter

the size of each slice would correspond to the proportion of data points belonging to that particular Priority

No Effect

Defects are considered based on the field ‘Issue type to identify defect’ which falls under Jira/Azure Mappings--> Defect Mappings

Defect Count by Assignee It shows the breakup of all defects within an iteration by Assignee.

Pie Chart

  • Slices represent count of defects by each Assignee

Agile Project Management

  • Jira

  • Azure Boards

No Maturity

No Filter

the size of each slice would correspond to the proportion of data points belonging to that particular Assignee

No Effect

Defects are considered based on the field ‘Issue type to identify defect’ which falls under Jira/Azure Mappings--> Defect Mappings

  • No labels