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.
Agile is empirical and decisions are made based on facts and also on progress. So KPIs are the facts which help in taking important decisions to make sure more value has been received by the users after each increment.
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. 👍
Very well Presented, Usually we deal with Burn-down, Burn-up, Through-put, Risk Matrix, But this is more valuable and covers all of the essential KPI's. Great Job !!!
In terms KPIs and metrics, I was only aware of Release & Sprint burn-down charts till date, but now I learned other things as well. Brilliant tutorial as it gives a vivid picture of data & facts driven Scrum framework. Thanks a lot.
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.
this is absolutely enlightening. thank you for breaking this down so much so that i now understand what the Scrum Metrics are and how they are calculated.
@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 for the teams who are transitioning from traditional way to story point estimation. Here they estimate in hours. Though the advice is to leave hourly estimation to story point over time, there are many organizations still feel comfortable using hourly estimation
Right at the beginning (26 seconds) you say this is video part 1, and in part 2 you will cover how you can generate and adapt this data in Excel. How do I find part 2 please?
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
Awesome work sir, It will help us a lot to build and understand the Scrum in our professional career. I just want to know how to take data into sheet and create matrix into spread sheet. If possible please share video or sheet.
Hi Niladri, Very well explained. I have one question for Defect leakage metric - @16:50 you mentioned defects identified during UAT testing but on the PPT on video, it says AFTER SPRINT CLOSURE. I am confused because UAT testing is part of Sprint right? Please clarify my question.
UAT is not part of scrum or sprints. UAT isn't even part of Agile. You can do UAT in a staging environment or production with Canary releasing depending on your product and user base.
Regarding the defect leakage, are we talking about the same defect which is raised both within the Sprint & SIT phase or are we talking about defects which are identified newly during SIT phase?
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!
@@AgileDigest So basically, at the end, team only worked for 40 hrs, because that's the time it took for them to finish the work. Be it over or under estimation, whatever the reason it. Right?
How do scrum metric integrate with traditional management KPI for management to use for budget and finance? How are these KPI used by management to manage?
Hi Niladri, I have a question,,, If planned SPs = say 40 SP and scope added = 5 SP, the commitment reliability should be calculated upon initial planned SPs ie 40 or on worked upon SPs ie 45?
This is very informative. I have a query for a project if we estimate by story points. Still do we take hours too? And in case of story point estimation what is the relevance of burndown chart?
Very Nice Video, .. I have a small question, In my project we donot assign hours to tasls, we just go by story points... so burndown reports doesn't give a good picture.... is there any other report which can help us in tracking the progress on daily basis!!!!
This is very helpful but for some kpis we are considering task hours and some SPs as per convenience. We can't confuse the stakeholders with two different measurement units.
hey ... very detailed and thorough explanation. However, I have one question which tool do you use to create such metrics? I mean any tool where we can provide the input and get the automated required metrics .... Please revert asap... Thanks in advance
Hi Very clear and informative explanation. Have a doubt for scope metrics. If in a single sprint a few story points are added & also a few are descoped. How to use Ur formula then??
Very good video. It was very crisp and clear. But i have a question, while calculating the velocity trends, you have explained about the upper bracket and the lower bracket. How do we take that? Please clarify.
Please define your average velocity as 100%, and make the upper bracket and lower bracket as defined, if it is 15%, then upper bracket will be 115% and lower will be 85%.
Clear measurements, well explained and depicted with right charts. Excellent video!
best channel ever on Agile methodology
Thank You
RIP to this man for speaking for 22 minutes straight without breathing.
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.
Agile is empirical and decisions are made based on facts and also on progress. So KPIs are the facts which help in taking important decisions to make sure more value has been received by the users after each increment.
Short but crisp... Very informative. Thank you very much.
So nice of you
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. 👍
Thank you, Siddhartha
Simply Fab !!! You have gained a Subscriber who is now a BIG Fan of you. Too good Content bro !!!
Wonderful video. Without your Videos scrum prep is not complete 🙏
Thank You
Each KPIs are very well explained. Very nice.
really nice. I was sceptical, but yes, I find some very valuable stats in here. Thank you very much!
Very informative content for people working on Scrum. Thankyou
Thank you
Superb & Brilliant explaination & Video..Fantastic Job Sir, Thanks for posting it..
Very well Presented, Usually we deal with Burn-down, Burn-up, Through-put, Risk Matrix, But this is more valuable and covers all of the essential KPI's. Great Job !!!
Glad it was helpful!
Excellent video on Metrics. Well explained and presented.
Glad you liked it!
One of the best video. thank you very much Niladri🙏
In terms KPIs and metrics, I was only aware of Release & Sprint burn-down charts till date, but now I learned other things as well. Brilliant tutorial as it gives a vivid picture of data & facts driven Scrum framework. Thanks a lot.
This video is out of the box. Fantastic explanations with perfect examples and templates. 💯
Thank you very much for sharing this knowledge. Cheers from Ecuador
Very nice video. Very useful, and clear. Thank you!
Excellent Explanation and very good metrics to measure. Fantastic work !!!
Glad you liked it!
Thanks! Was just looking out for something like this. Keep up the good work Sir!
Thanks, will do!
This is a very awesome video...What else would some one be looking out for? Great stuff. ✔❤
Thanks so much!
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.
Very clear demo of KPI measurment and good coverage. Well done.
this is absolutely enlightening. thank you for breaking this down so much so that i now understand what the Scrum Metrics are and how they are calculated.
Awesome presentation.. great work.
Thank You
Very useful and thank u so much for nice explanation
Excellent and well defined..Thanks
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.
Thank You
Very brief explanation, good job. Thanks!
Glad it was helpful!
Really a nice compilation and explanation of useful metrics that are comprehensive enough
Thank You
Simple and very informative. Thanks for explaining all metrics very well.
Excellent video! Thank you so much!
You're very welcome!
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?
All are still there, only the menu positions are changed. Look for self study section
Really Good content ..
Will help in Quality Management for Agile projects
Love this! Easy to follow and it make sense.
Thank You
Excellent, Its clear, concise, and easy to understand. Thanks for sharing your knowledge.
Good pace and to The point !!
this is awesome video. very useful
Thank you
Excellent video. Thanks much for uploading.
very well thought through ... Can we apply these metrics in SafeAgile world as well ?
Nice video :-). Can you help me the tools you have used to create such nice graphs and dashboards without using commercial tools ?
Hi Bubunia, Its all in Excel Only.
@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 for the teams who are transitioning from traditional way to story point estimation. Here they estimate in hours. Though the advice is to leave hourly estimation to story point over time, there are many organizations still feel comfortable using hourly estimation
Please share link to Part 2, want to see the practical usage and generation of these KPIs
Sorry , I am not sure what you really looking for.
Very impressive. Great explanation.
Thank you a lot for explaining!
Thank You
Right at the beginning (26 seconds) you say this is video part 1, and in part 2 you will cover how you can generate and adapt this data in Excel. How do I find part 2 please?
Thanks a lot Sir!!🙏🏻🙏🏻❤️❤️
The video was really informative.
Wonderful, just a quick query, do Jira provides this kinds of metrics or dashboards?
Pls guide on that front.
No jira does not
Excellent video! Very helpful....
This is something I was looking from long, thank you.
Thanks for upload this kind of content! Regards from Argentina :)
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
Very impressive. Just in time training for me as I am implementing Quality Plan on my project.
Awesome work sir, It will help us a lot to build and understand the Scrum in our professional career. I just want to know how to take data into sheet and create matrix into spread sheet. If possible please share video or sheet.
This is not scrum…don’t even think about doing these metrics. Velocity and burndown charts are enough
Really Insightful. Thanks for sharing the video.
Thank you
Hi. Thanks for this tutorial. My Reports are not showing completed issues. Please what could possibly be this problem? Thanks for your response.
Please send us a email to support@agiledigest.com with necessarily detaila
Excellent explanation. thanks for making such wonderful video.
Thank you for sharing this information.,it is very useful and interesting for me.
Very clear and excellent explanation.
The concept was explained by very nice and able to understand easily, really useful thanks much
What's the data set that I need to use to get the "Monitoring the Flucuation"
Just the velocity and individual sprint Completed story point. Make some upper sigma and Lower sigma as tollarance boundary.
very well explained
Very useful video, Thanks for sharing
My pleasure
superb video
Thank you so much 😀
Awesome video
Thanks for the visit
wonderful explanation
Can we use Story points instead of hours for calculating capacity utilization ?
Useing story point is a better or mature approach, in that case you don't need capacity utilisation
Very nice explanation. thanks!
Very good video
Thanks
Can you create another material using story point, using hours to estimate story is obsolete, particularly Velocity and Capacity.
velocity is already there in this template. few practices uses Hours, if they want they can use it. just a reminder don't mix them up
Hi Niladri, Very well explained. I have one question for Defect leakage metric - @16:50 you mentioned defects identified during UAT testing but on the PPT on video, it says AFTER SPRINT CLOSURE. I am confused because UAT testing is part of Sprint right? Please clarify my question.
UAT is not part of scrum or sprints. UAT isn't even part of Agile. You can do UAT in a staging environment or production with Canary releasing depending on your product and user base.
Very informative, with visuals, thank you.
very knowledgeable thanks for sharing
very well explained sir, thanks. Do you plot all these graphs in JIRA or excel sheet?
Excel
They might be a little complex, but excel can do all these a combination of charts styles
Regarding the defect leakage, are we talking about the same defect which is raised both within the Sprint & SIT phase or are we talking about defects which are identified newly during SIT phase?
new defects
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!
Utilization is correct, variance is how much you estimated and how much the work actually took, over estimation or under estimation.
@@AgileDigest So basically, at the end, team only worked for 40 hrs, because that's the time it took for them to finish the work. Be it over or under estimation, whatever the reason it. Right?
can we use these metrics across all methodologies ..like kanban or Agile
This is designed for Scrum only.
In that please give a talk on architect team in agile release
It's very useful to me. Thanks
Glad to hear that
Super video ..great
How do scrum metric integrate with traditional management KPI for management to use for budget and finance? How are these KPI used by management to manage?
Do we have any JIRA add-on that can provide these stats?
Hi Niladri,
I have a question,,, If planned SPs = say 40 SP and scope added = 5 SP, the commitment reliability should be calculated upon initial planned SPs ie 40 or on worked upon SPs ie 45?
This vid was very helpful. Thank you uploading it.
This is very informative. I have a query for a project if we estimate by story points. Still do we take hours too? And in case of story point estimation what is the relevance of burndown chart?
you are a lifesaver
Thanks a lot Niladri ....
pls share xl template
wow, great content.... keep it coming
Thank you! Will do!
Very Nice Video, ..
I have a small question, In my project we donot assign hours to tasls, we just go by story points... so burndown reports doesn't give a good picture.... is there any other report which can help us in tracking the progress on daily basis!!!!
for sprint burndown, Hours is better
This is very helpful but for some kpis we are considering task hours and some SPs as per convenience. We can't confuse the stakeholders with two different measurement units.
Well explained..
Very helpful and descriptive
Excellent!!!
HI I NEED the presentation please
hey ... very detailed and thorough explanation. However, I have one question which tool do you use to create such metrics? I mean any tool where we can provide the input and get the automated required metrics .... Please revert asap... Thanks in advance
Thank you Anu. You can get the excel template here agiledigest.com/product/scrummetricstemplate/
Sir please give a talk on Agile release train
Are these JIRA default reports or are you using any reporting plugin?
Hi
Very clear and informative explanation. Have a doubt for scope metrics. If in a single sprint a few story points are added & also a few are descoped. How to use Ur formula then??
any changes on commitment should be counted. plus 2 and minus 2 will not make it zero. It will show both as scope changed.
Very good video. It was very crisp and clear. But i have a question, while calculating the velocity trends, you have explained about the upper bracket and the lower bracket. How do we take that? Please clarify.
Please define your average velocity as 100%, and make the upper bracket and lower bracket as defined, if it is 15%, then upper bracket will be 115% and lower will be 85%.