DEV Community

Cover image for Agile Metrics
Do it!
Do it!

Posted on • Updated on

Agile Metrics

Scaled Agile’s first principle is taking an economic view talks about
achieving the shortest sustainable lead time with the best quality and value, we can attain that by measuring using Agile metrics.

What are Agile Metrics and why is it important?

The agile approach is based on the iterative and incremental software development principle, which means the future work builds upon the previously done work (& feedback).
Agile metrics are the standard of measurement to see how productive a team is and to predict future work that can be done.

achieving the shortest sustainable lead time with the best quality and value.

Below are the metrics I care about:

  1. Happiness Metrics: Research suggests, happy people, give ~ 12% better output. To tap on that elusive 10-12%, I care about it. Happiness metrics can be introduced as part of the retrospective meeting and we can build a history. It’s a holistic approach (more than retro) and opens up the forum for a bigger discussion. An article where I show to design one for your team.
    Happiness Metrics

  2. Capacity along with Velocity: Resource Capacity, along with a steady velocity helps to plan for future sprints. Capacity shows the resource availability and steady velocity displays signs of a mature team, with which one can predict what work will be completed and when. An article which talks about agile capacity planning for sprints.
    Agile Capacity Planning

  3. Throughput and blockers: Throughput is the number of tasks completed within a given period (usually a sprint) and blockers are the impediment that prevents a task to be completed. This metric can be used for both New Projects as well as monitoring and support. I care about it as it tells why the task was not completed. It identifies a blocker, which can be dependent on a team, environment, or pending requirement clarification. Throughput can be measured via story points or work in progress (WIP) items.

  4. Cycle and Lead Time: These metrics fall in the realm of monitoring and support projects. Cycle time is the time taken from when the task was requested when it was completed. Lead time is the time taken by the person to complete the task. I care about the cycle and lead time to see how well the task was understood, the skill level and efficiency of the person.
    Cycle time varies based on priority and amount of work still in the pipeline. If a team is managed properly, this metric can give a response to the business question of “when will the work be completed ?”.

Did I miss some that I should care about?

Top comments (0)