4 useful metrics for Agile Software Development teams in daily scrum

Your team uses the Scrum framework for Agile Software Development

The Scrum guide describes Daily Scrum as a 15 minute time boxed event to plan the next 24 hours for the development team.

Scrum is founded on empirical process control theory. Three pillars uphold every implementation of empirical process control: transparency, inspection and adaption.

Three pillars of Empiricism

Three pillars of Empiricism

The daily scrum is a classic example of using these pillars.  The Agile Software Development Team plans work for the next 24 hours.

This optimizes team collaboration and performance by inspecting the work since the last Daily Scrum and adapting upcoming Sprint work.

To inspect there should be full transparency.

While the Agile Software development team is sharing this information with each other, an information radiator helps amplify inspection of the data required to plan future work.

At a Glance Jira DevOps Dashboard  – A key information radiator during team’s daily scrum

The Development Team uses the Daily Scrum to inspect progress toward the Sprint Goal and to inspect how progress is trending toward completing the work in the Sprint Backlog.

Sprint progress

1. Sprint progress: stories and defects from Jira

But wait, is that enough? sure but what about what changes are happening in the code like Commits and Pull Requests in the Sprint?

commits pull requests

2. Sprint progress: Commits and Pull Requests from Git

The Daily Scrum optimizes the probability that the Development Team will meet the Sprint Goal. Co-relating what has been committed and merged into the main branch with the stories and defects gives the team confidence that the work done is leading them towards the sprint goal.


Besides quantity of code should we also inspect code quality and should it be transparent? Absolutely

code quality
Test coverage

3. Sprint progress: Code Quality and Test Coverage from Sonar

This metric is really key to track almost daily so that critical bugs, reduced test coverage and other issues might be caught quickly and fixed before the sprint comes to an end. This is required for maintaining good quality code

Of course if you are going to really be Agile, the team needs good continuous integration and continuous delivery practices. Which means that they need to track their builds and deployments in various environments during the sprint.


4. Sprint progress: Builds success, build times by developer from Bitbucket Pipelines

Every day, the Development Team should understand how it intends to work together as a self-organizing team to accomplish the Sprint Goal and create the anticipated Increment by the end of the Sprint.

If a consolidated dashboard is on a large screen where the team does its work, there is complete transparency into the development process and the team can continuously inspect and adapt its working.

At a Glance DevOps dashboard that brings data from the different systems as a dashboard in Jira

What does yourAgile Software Development Team think of our plugin? If you haven’t tried it yet, you can download it at Atlassian Marketplace. Would you want us to extend it for your teams. Please let us know your feedback by answering 7 short questions  at https://www.surveymonkey.com/r/T5Z25SL

Your comments and feedback are valuable, so please let us know what you think.



Shares 0

Leave a Reply

Your email address will not be published. Required fields are marked *