Sprint Burndowns by Story Points?

Edit Subject

I like to do sprint burndowns by story points remaining (rather than hours remaining) but couldn't find a way in SWP to do this exactly. The closest we came was to use the Release Burndown by Date feature, which is like an expanded version of what I am trying to achieve. Caleb suggested if there was an option on this report to limit to a single sprint, this could essentially be a burndown by story points, which is what I am trying to achieve.

The way I explain it in my class, these are the stories the team "asserts" are done. So, in essence, they are telling the Product Owner "We assert this 8-point story is complete and we will be presenting it to you in the Review meeting to see if you agree." This is much more useful to me as a PO than knowing, really, any task detail. As a PO, I care about my backlog items being done. If I am a very non-technical PO, I might not even understand the tasks, but I do understand the feature itself.

In my SM days, I worked with a number of teams who were so used to doing, really, whatever they felt like as individuals, that they simply could not comprehend the concept of finishing an entire story. These individuals were all about "me" and not at all about "we", meaning the team and its commitments. Changing the burndown to move when backlog items were completed kind of jolted them out of this.