Understanding Scrum Metrics and KPIs - Agile Digest

really nice. I was sceptical, but yes, I find some very valuable stats in here. Thank you very much!

Simply Fab !!! You have gained a Subscriber who is now a BIG Fan of you. Too good Content bro !!!

Awesome presentation.. great work.

i must thank u for the awesome video what an explanation, i hope to see more such videos by u , great job👍thanks a lot.

let me correct in calculating velocity sum of 6 sprints is equal to 156 not 157, though outcome is correct, just correcting so that no one gets confused.

best channel ever on Agile methodology

What's the data set that I need to use to get the "Monitoring the Flucuation"

Very informative content for people working on Scrum. Thankyou

Being a Scrum Master with 5+ years of Agile experiences, I am delighted to see such an insightful and authentic representation of these various useful Metrics in this presentation. I must say, this is well thought of, properly researched as per Organization standards and clearly explained. This video is not just useful to make one 'interview ready' rather to be appreciated beyond its effectiveness for the real world work in the industries. Kudos to Niladri for his dedicated hard work. My strong recommendation to Agile practitioners, consider this is as a 'must watch (follow)' video for your knowledge-bank. 👍

@agiledigest if you are using hours tor work out capacity utilization does that mean you estimate in hours too? Or has capacity uitilization not related to estimation at all? Because if we estimate in story points, where do hours come into play now?

this is awesome video. very useful

Very good video

Very useful!

Awesome video overall, super helpful.

Small correction on the Over Estimation and Under estimations formula. It should be subtracted by 100 not multiplied by.
Over Estimation: (E-A/E) - 100
Under Estimation: (A-E/E)-100

Please share link to Part 2, want to see the practical usage and generation of these KPIs

This is a very awesome video...What else would some one be looking out for? Great stuff. ✔❤

I saw someone's comment stating that why should we need many metrics when working software itself is a metric and that's alone is good enough to have.
Look at this analogy - Goal is to stay healthy (refer to: Goal is to deliver working software). To achieve this, you need to measure the current or past health condition. You cannot control or improve when you cannot measure. There Metrics will help to understand the current status, which in-turn helps to analyze on improvements and reflects our progress towards goal. One cannot simply say out of the box, I achieved my goal and I am healthy. You should be able to significantly show the improvement from your previous condition to the current improved condition.
Metrics will help to -
Understand the current status
Analyse the insights on improvements
Reflects our efforts if they are moving in expected direction or not.

Please share the link for downloading templates

It's very useful to me. Thanks

This is the exact reason developers hate Scrum. When you take metrics like these people work towards the metrics, not towards what the actual job is.

Agile was made by developers for developers, not for management.

Excellent video! Thank you so much!

Thanks! Was just looking out for something like this. Keep up the good work Sir!

Awesome video! Truly appreciate your work in helping others.
I'm still confused with 2 things here. Between Capacity Utilization and Estimation Variance.
Capacity Utilization measured considering efforts in hours team actual capacity (220). However, team committed (which means team used) (130). Am I correct?
Estimation Variance again measured considering efforts in hours team committed (130). But, only worked for 40 hrs? What did they do for rest of the 90 hrs?
Meaning in total team should work for 220 hrs but only worked for 40 hrs? Is my understanding correct?
I'm new to these metrics, hope you can help me in clarifying the question. Thank you!

superb video

Informative but talks too fast with no pauses. It's a lot of information being thrown out, so allow pauses for people to digest what you are talking about.

Nice video :-). Can you help me the tools you have used to create such nice graphs and dashboards without using commercial tools ?

Wonderful, just a quick query, do Jira provides this kinds of metrics or dashboards?
Pls guide on that front.

Can you create another material using story point, using hours to estimate story is obsolete, particularly Velocity and Capacity.

Very well explained! Earlier there was article by you on the same topic on your portal. Don't see that anymore. Where can we get it?

Short but crisp... Very informative. Thank you very much.

Awesome video

Thank you a lot for explaining!

Excellent, Its clear, concise, and easy to understand. Thanks for sharing your knowledge.

This video is just marvelous. It describes very import concepts which normally we don't get to know. Thank you so very much for sharing your knowledge with us.

Simple and very informative. Thanks for explaining all metrics very well.

Thanks a lot Sir!!🙏🏻🙏🏻❤️❤️
The video was really informative.

pls share xl template

Informative.

Awesome !

Very good knowledge video. But you need to slow down a little. You talk too fast, and jump on to the next statement, immediately, without any pause.

very well thought through ... Can we apply these metrics in SafeAgile world as well ?

Each KPIs are very well explained. Very nice.

wonderful explanation

In that please give a talk on architect team in agile release

Sir please give a talk on Agile release train

Excellent!!!

Can we use Story points instead of hours for calculating capacity utilization ?

What’s the use of measuring so many metrics when you are following scrum? These metrics don’t make any sense when you want to implement agile in true sense. I think you know already that working software is the true measure of progress in agile? Velocity, velocity trend and commitment reliability should be enough to understand the health of sprints. Burn-down chart already talks a lot on how the overall implementation went. Capacity utilisation are typical project management(non agile) metrics. Organizations that doesn’t understand agile principles and recruit scrum masters to drive projects demands these kind useless metrics.

It's such an important topic.. Your contents are really good but delivery of content is poor.. You're in so hurry .. As if you are reading a news bulletin.. Please check your pace.