Creating an agile report - planned points vs actual points completed

[#1]

I have attached screenshots to explain what I am trying to do.

This screenshot shows the progress of last week’s sprint. Even though everything is in the complete column, you can see that it says 92% complete.

This is representative of the story that was not completed and was then moved to the backlog to be considered for the next sprint.

Meanwhile, if you view all iterations, the total points and points completed would lead one to believe that the sprint was 100% complete.

I am looking for either a report or a view that will help show the planned progress vs the actual progress over the course of several sprints.

Let me know if you have any questions.

Thank you.

Darcie

[#2]

Agreed - this would be helpful. Right now, our only way to do this is to manually note various points statistics (i.e. committed points at the beginning of a sprint)

[#3]

It is not clear how to even do that. I am running weekly sprints and I have no way to determine if we are overcommitting or estimating accurately.

[#4]

I know what you mean. This may be a given, but we're just recording the data at this point and looking back at prior sprints to consider how to estimate for the next. Over the next 2-3 months, we'll have a better idea of what "normal" is with a 100% focus. Just creating a custom form with a few data points may help you in the meantime. For instance:

• Points Committed (started sprint w/)
• Points Completed
• People/Days (i.e. if you're counting on 6 hours/person/day, then each person counts for 0.75/day).
• Points/PersonDay - Points divided by People/Days available in that sprint - this gives you an idea of how many points per person your team is completing after adjusting for people being OOO.

Ignore if you're already doing something like this!

[#5]

This really should be a standard feature!