Graph of true Committed vs Actual

[raffidavidow]

I am wondering if there is a way to see the velocity chart or something like that but showing the story count at the beginning of the sprint vs the actual completed BUT against the same stories that were committed and then visually showing the new points added or removed during the sprint. 

I know you can kind of see this in the sprint report but its a manual process and sprint by sprint and I am really looking at something across the last 6 sprints so I can look at the impact of things constantly shifting during a sprint.  

Any ideas ? 

[Andy Heinzer]

Hi,

I understand that you are looking for a report to try to see the differences between issues committed to at the beginning of a sprint vs those actually completed in that sprint.  The velocity report is good for letting you understand how fast your team is moving, but it doesn't really show you what you are looking for in this request.

Instead, I would suggest trying a different agile report such as the Burndown report.  Provided that you are estimating some value for these issues before the sprint starts (time or story points), the burndown will track the issues at the start of the sprint and also keep track of any scope changes, such as issues added to the sprint after it is started, or issues estimates that change mid-sprint.  An upward jump of the red line in this graph is a pretty clear indicator that something was added after the sprint was started.

While that report is good for viewing on a per sprint basis, the Epic Burndown report is better for seeing this across several sprints.

I hope this helps.

Andy

[raffidavidow]

Andy - While a burn down or burn up report helps me for that specific sprint - I am looking for this data across multiple sprints. Kind of like the velocity report (but that looks like it can be changed if someone goes after the sprint and updates issues) i am really looking for a "what really happened" report where I can see commitment reliability against scope that was originally committed to and scope that was creep during the iteration.  Does that make sense ?

[raffidavidow]

Hit enter too soon - i want to see this across multiple sprints that have multiple epics in them (so i dont have to build this info manually)

[Andy Heinzer]

Thanks for the additional clarification.  I still think that the Epic Burndown report can help here.  It does at least span across several sprints to help you see how much effort is put forth in each sprint of an epic.  And furthermore, the color coding there can help you identify when scope changes happen. These scope changes can help to identify when the scope of that sprint changes in terms of the amount of work planned. 

But admittedly this single report is not intended to span several epics.  And if you are trying to see this kind of information across several epics at once, that report is not going to be as helpful here.

Perhaps there are a few apps in the Marketplace that might be better able to meet that need today.  I was looking through and I came across the Agile Velocity Chart Gadget and the Individual Velocity Report/Chart Gadget.  Each gadget appears to offer some alternatives in regards to how you can measure velocity.  It sounds like this is more along the lines of what you are looking for, but admittedly I have not used either of these personally.  They do both appear to offer some more in depth configuration options that might be better able to show you the information I think you are seeking here.