Avoid output-based Agile metrics and embrace outcome-based ones.

We have seen many productivity metrics used in the Agile world. To begin with, Velocity, Escaped defects, Burndown charts, Defect ratio, etc. These are all output-based metrics, and it is not connected to any outcome.

Above all output-based metrics can be easily manipulated and inflated. It is better to use the following metrics to measure the health and productivity of the projects.

Testing Lead Time

We have seen an elaborate cycle for various testing in highly regulated industries like the Financial and Pharmaceutical domains. It starts with Quality testing (QA), Integration testing (SIT), User Acceptance Testing (UAT), and product testing before it is released to end users. Sometimes, this testing phase consumes more time than the overall execution of the project.

Involving the testing stakeholder during the upstream process than the downstream will reduce the long testing phase.

Rework Effort

Along with the elapsed time, we need to measure the rework effort due to bugs in various testing phases. Just keeping a tab on the bug count will not help. Instead, we need to measure the time and effort spent on fixing the bugs. These rework efforts can spread across ST, SIT, UAT, and production.

Lower rework effort is a powerful indicator of the health of the project.

Deployment Time

It is pivotal to measure the time it takes for a feature to move from creation to production. This metric tells us how agile the team is and how tuned is the engineering process to help turn a feature into reality. Less deployment time is inversely correlated to the team's stress.

Long deployment time during the weekends is not a good sign productive team.

Deployment frequency

To get an idea of the deployment frequency, we need to ask the team how frequently you make a production release? Is it daily, monthly, quarterly or yearly.

Faster deployment cycles will help understand how fast the team can push the backlogs.

--

--

--

Tech enthusiast, Project & Product Management. Interested in Management, Economics, Psychology, Philosophy, Human Nature, Behavioral Economics, almost anything.

Recommended from Medium

Methods to find HTML objects with Selenium

Why validating data at backend is most important?

The FHIR Protocol

Deploying a Dojo App with Docker

My First Hacktoberfest Entry

😎Are you ready to play #WSGToken’s DUNK IT with me guys?

Kubernetes Networking Debugging with Java SpringBoot MicroServices

TinyML: TVM taming the final (ML) frontier

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Ranjit Damodaran

Ranjit Damodaran

Tech enthusiast, Project & Product Management. Interested in Management, Economics, Psychology, Philosophy, Human Nature, Behavioral Economics, almost anything.

More from Medium

Turning failure demand into value demand

Results Matter #3 — Agile projects built upon by the collective intelligence of the people

“Budgeting”

Scrum for Small Teams with Multiple Stakeholders and Projects