Parasoft’s Development Testing platform included functionality to track user stories. In order to make this information available on the dashboard, we needed a visualization similar to an iteration burndown chart.


  1. Keep track of how many story points your team is completing each sprint.
  2. Keep track of how many story points are added into the release each sprint.
  3. Predict when the release was going to be completed.

No additional work

Crunch time

Sometimes there are urgent features that need to be added to the release. The baseline shifts down as more stories are added to the release. This allows separate measures for a teams velocity and the increase in the amount of work.

With additional work