The metrics should be a combination of project-related metrics, as well as business metrics that help to view the progress of the team.  

Here’s a list of the most important metrics: 

1. Sprint Burndown 

The burndown chart is a graphical illustration of the predicted Scrum tasks as compared to the actual tasks completed. The volume of work left is plotted versus time for the duration of the sprint. The output in the duration of hours, story point, or backlogs remaining can be calculated which enables tracking the real-time progress of the sprint.  

2. Lead Time 

Lead time is the duration of receipt of the requirement and its successful delivery. This includes the time duration from the actual commencement of the development process to the end of delivery.  

Lead time and cycle time are popular Lean and Kanban metrics that help to identify potential bottlenecks within the process. It also PROVIDES STAKEHOLDERS and clients necessary insights about the estimated VELOCITY of development. 

If the lead time is low, then the requirement moves faster from the BACKLOG to the development phase, and this then lowers the cycle time and hastens the development process. 

3. Flow Diagram 

Cumulative flow is an essential Kanban metric for assuring a steady flow of work across the team. The cumulative flow diagram provides information for bottlenecks at any stage and is instantly envisioned and the work in progress is more easily tracked. 

The intricacies can be tracked on a real-time basis during the process. The problem resolution and analysis take place instantly. 

4. Sprint Velocity 

Velocity is a measure of the amount of work the development team is able to perform in a given period of time. Velocity is an important metric; but it is relative and cannot be used as a measure of COMPETENCE or performance of the agile team.  

5. Failed Deployments 

Failed or unsuccessful deployments are the deployments that fail to get pushed over a given period of time. These failed deployments can be calculated over a week, month or depending on the recurrence of your releases. 

6. Code Coverage 

Code coverage aka test coverage provides a much-needed view of the amount of untested code in your codebase. It is not a measure of how good your tests are but gives a rough visualization of the code that is incorporated by unit tests. 

7. Net Promoter Score 

NPS is a business metric that represents the likeliness of your customers to refer to their contacts. Customer analysis and collection of feedback are crucial in the calculation of the Net promoter score.