Tuesday, Aug 4 2020 | Time 08:54 Hrs(IST)
  • Aurangabad reports 98 fresh COVID-19 cases, 14,992 in total
  • Chinese mainland reports 36 new confirmed COVID-19 cases
  • 763 fresh COVID-19 cases, 12 fatalities in eight districts of Marathwada
  • Wanda Diamond League in Doha rescheduled for September 25
  • China's Yan sets up clash with world number one Trump at Snooker World Championship
  • Five-time Olympic diver Terauchi tests positive for COVID-19
  • Notorious criminal Vicky Chauhan shot dead by unidentified men in Nanded
  • 447 new corona positive patients detected in Kolhapur
  • Body of 40-yr-old man with stab wounds found in Nashik
  • Covid-19 cases in Nashik rises to 16K
  • Covid-19 cases in Thane surpass 90K
  • War against COVID-19: MP’s body count rises to 900
  • 14-day lockdown in Hingoli from Aug 6
Press Releases

What statistics and metrics should a scrum master track?


It has been rightly said that one cannot improve in case one does not measure. The project progress can be measured with the help of key performance indicators as well as achievement of milestones depending upon the individual contributions and the overall contributions of the team.


The scrum certification helps to define different kinds of milestones so that progress can be measured, and the overall project is successful. This will allow the team members so that they can inspect and adapt how to do things and when to do things.


 Following are some of the metrics which the scrum master should track so that highly informed decisions can be made:


 - The stories which have been completed and committed: The first and most important metric is the ability of the team so that it can understand as well as predict the capabilities. To measure these different kinds of committed and completed stories have to be compared and have to be identified during the whole sprint review.


 - The technical debt management of the organization: This is another important metric which has to be considered so that different kinds of problems and issues faced by the organization can be delivered at the end of the sprint. This can be measured with the help of several bugs and can also include things like the material of training and user documentation.


 - The velocity of the team: The consistency of the team will depend on project to project. This can be calculated with the help of comparisons drawn for different story points which have been completed in the current sprint and the previous sprint. The basic aim should be +/-10%.


 – The quality which has been delivered to the consumers: At this point of time the organization should understand that whether are they delivering the things depending upon the consumer needs or not. It should also focus on providing value to the consumers at each point. The best way of measuring these metrics is by serving the consumers as well as stakeholders so that their satisfaction level can be understood.


 - The enthusiasm of the team: This is another important component for the whole team and can be a reason behind the success of the team. In case the team is not enthusiastic then none of the methodologies can help in achieving the goals. The enthusiasm of the team can be measured with the help of observation at different sprint meetings or by following a straightforward approach which means to directly ask the team members are they happy or not.


 – The retrospective improvement of the process: The scrum team should have the ability so that the development process is revised and made more effective as well as enjoyable. This can be measured with the help of performing account of retrospective items. The commitment of the team can also be addressed with the help of this concept.


 – The understanding of the team about the goal: This is a very subjective measure and the goals should be aligned with the value providing to the consumers. This can be best determined with the help of day-to-day interactions and feedback from consumers.