RTC Story Burndown Report Question
I am using the built in RTC Story burndown reports. Some times, we end a sprint with technical debt. I want to be able to monitor and make sure the technical debt is taken down in the next sprint.
One answer
I am not quite sure what you mean with the datasnap being forced after the iteration ends. The iteration is done and an iteration burndown only considers work done during that iteration. Work done after the iteration will not show up in the iteration.
Comments
We are carrying the technical debt to the next sprint, but the story points for technical debt gets added to the new work for the next sprint.
I would not recommend using that approach. This requires the team to be working against two plans ... one for the previous sprint and one for the current sprint. It also makes it hard for you to use some of the built-in widgets, that depend on there being a single "current" iteration. Instead, I would recommend using the approach described by Ralph of having those technical debt items planned for the current iteration ... if you want those items done first, just rank them highest in the plan.
1 vote