Skip to main content

Agile Metrics

Last post 07:43 pm June 12, 2020 by Dima Santarskyi
8 replies
07:01 am August 8, 2015

Does anybody has idea about Agile Metrics that being track during execution apart from tracking BD chart and team velocity?


11:19 am August 10, 2015

Dear Sushil,

The main metric in Scrum (and most other agile processes) is the done increment.

It tells us the truth about the status of the project.
In forecast based processes we needed a lot of metrics to tell us if we still stick to the plan. We all know how significant those plans as well as these metrics were…
Management does often not understand the big advantage of seeing actual working software that meets a definition of done and they still want to see meaningless numbers instead. Convince them, that those are not needed anymore.

Scrum believes in change and welcomes change.
So what we should ‘measure’ are changes to our plans, the product backlog.
After each Sprint Review, we can have a Product Backlog Change Report, that describes what has changed in the Product Backlog and why.

Hope this helps
Sebastian


11:24 am August 10, 2015

It appears that the term "Agile" is being used rather broadly, so allow me to focus on just Scrum....

Scrum does not mandate the use of burndowns or velocity.

I'm seeing some redundancy in repetitive posts here --
https://www.scrum.org/Forums/aft/1545

Would you like to continue in the thread above, or prefer doing so here?


06:44 am February 13, 2016

Metrics can be tricky - you always need to remember they are not the ultimate goal - only signs to spot if you are on track. Here you can find couple of useful things which organisation should think about

https://www.scrum.org/Blog/ArtMID/1765/ArticleID/14/%E2%80%98Evidence-B…


02:07 pm February 23, 2016

A quote from Albert Einstein:

"Not everything that can be counted, counts. And not everything that counts can be counted."


02:32 pm February 24, 2016

Amen to that Timothy!


10:35 am May 16, 2019

I advise everyone to read the article on this topic from the company Jelvix. Link here: https://jelvix.com/blog/9-fundamental-agile-metrics

Yes, and with the work of this team in general, read. Explanatory developers from Ukraine, I assure you :)


01:15 pm May 24, 2019

In order to measure the success of agile programs, our team uses the following five metrics, which so far has proved to be effective:

1) value to the business

2) timely delivery

3) customer satisfaction

4) product quality

5) visibility

 


06:10 pm June 12, 2020

Thanks for useful information


By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.