A Sprint Burndown widget with everything you’ve been asking for

Gregg Boer

Gregg

With Sprint 160, we are releasing a new Sprint Burndown widget that lets you choose how to burndown for a sprint.

Azure DevOps Sprint Burndown widget - configured by Count of Tasks

You can burndown by Story Points, count of Tasks, or custom fields. You can create a burndown for Epics, Features, and Stories. In fact, you can burndown by summing any field or by counting any type of work item. The new widget displays average burndown, % complete, and scope increase. You can choose to burndown on a specific team, which lets you display sprint burndowns for multiple teams on the same dashboard. With all this great information to display, we let you resize it up to 10×10 on the dashboard

Azure DevOps Sprint Burndown widget - Configuration

You’ll notice that we have two versions in the widget catalog.

Azure DevOps Sprint Burndown widget - Widget Catalog

The new version requires access to Analytics. Since some customers restrict “View Analytics” permissions, we kept the legacy version as a backup option for them.

To try the new version, you can add it from the widget catalog. Or, you can edit the configuration of an existing legacy Sprint Burndown widget and check the Try the new version now box.

Azure DevOps Sprint Burndown widget - Easy upgrade to new version

For more information, check out our docs.

We know many of you have been asking for these features for a while. We are so happy to provide them. Enjoy!

10 comments

Comments are closed.

  • Avatar
    Timothy Scott

    On the new sprint widget, I cannot get the chart to scale correctly. You have a max value of 30 on your example, but my top scale is around 250. (when have only 50 story points in sprint)?

    • Avatar
      Timothy Scott

      Determined the scale (y axis) is incorrect because it is using the “capacity” value – an hours metric. We still estimate hours on tasks, but are using story points for the parent. We do not measure story point capacity for each individual. Trying to transition away from hours, but not there yet.

      • Gregg Boer
        Gregg BoerMicrosoft logo

        Hey Timothy,

        I want to make sure I understand your comments. You are correct, the y-axis is based on whatever you selected for “Burndown On”. If you “Burndown On Remaining Work”, then the scale should adjust appropriately. Do you still have issues or unanswered questions?

        • Avatar
          Mark vM

          Hi Gregg, there is a bug in the y-axis. I have selected Burndown On “Sum of Story points”.
          But the y-axis shows the hours capacity for the team.
          No matter which selection i make in the Burndown On combobox, the y-axis never changes.

          This way the chart becomes pretty unusable as it looks like this:
          https://imgur.com/a/aWkduVx

          In this case our team capacity is 496 hours.
          While we have added a total of 28.5 story points to the sprint.

          • Avatar
            Saurabh JainMicrosoft logo

            Hi Mark,

            This is happening as we are showing different units(hours and story points) on the same y axis (this is by design to keep graph simple).

            To make graph usable you can try following things:
            1. If we disable/unselect the green legend the y axis on graph will change appropriately.
            2. Teams can Configure Story points and capacity to use same unit either hours or points.

            Please let us know if you need any help.

          • Avatar
            Mark vM

            Hi @Saurabh Jain,

            Thanks for the reply.
            1. I don’t see a way to disable that. When i open the configuration for the widget, there is no way for me to do that. Am i missing that?

            This is an option i don’t prefer. We like to use Story points for our workitems, and hours for our actual availability.