locked
Burndown chart wrong due to rescheduled backlog item?

    Question

  • Hi, I started the first Sprint but the team could not finish some sprint user stories. So I moved them back to the product backlog and added to the second Sprint. However, the effort for those stories did not change. Thus burndown chart for Sprint 2 was generated as if the Sprint had more effort than the actual amount of effort. Let me say that we concluded 80% percent of the stories, but the burndown chart did not count 20% of the stories. Otherwise it counted 100% of the effort.
    How is the better way to have proper information about team progress during the Sprint in cases where some stories came from past Sprint?
    Tuesday, November 14, 2017 1:48 AM