Sprint Burndown - monday.com

Overview

A burndown chart displays the amount of work in a sprint that still remains and also the work that has been completed. This is a big help for your team because they can handle the progress, predict if they can finish the goals and make them aware of scope changes.

  • In the horizontal axis (x axis) the period of time in days that the sprint lasts.

  • In the vertical axis (y axis) the amount of work planned (i.e., estimated) for the sprint in the estimation statistic you choose when configuring the gadget. The unit of measurement can be: Story points or issue count.

The lines in the chart:

  • Remaining work/effort: The green line represents the total amount of work or effort left in the sprint, according to your team's estimates in either story points -column Estimated SP- or issue count. Here you should check if it increases, which indicates scope creep i.e., growth in the scope of the sprint.

  • Actual work/effort (optional): The yellow line represents the actual work or effort carried out in the sprint. If your team’s estimates are in issue count, it’s the same as the remaining work. However, if you chose story points, this line takes the real story points in the column Actual SP

  • Guideline, the blue line. This line is a guide for your team to approximate where they should be to finish the work on time, provided the work was done in a linear progress. The ideal amount of work left or ideal burn rate.

Not to mention that ideally, your team’s green line should be below the blue line. Meaning that they are on track to finish everything online before the end of the sprint.

Configuration

Name your gadget meaningfully, so everyone knows at a glance what it is about and when to use it. Fill out the rest of the fields as applicable, namely:

  • The datasource, indicate the monday.com account where you want to fetch the data from.

  • The workspace and board where the sprint is located. The workspace has to be from monday.com dev, and the board Sprints is required. Select one of the sprints.

  • The estimation statistic, choose how your team estimates the how much work is committed in a sprint:

    • Story points (Estimated SP column). Your team will burn down the story points estimations they did.

    • Issue count. Your team will burn down the number of issues completed (when the column Status is Done). And they won’t need to enter estimates in the backlog.

  • Finally, indicate if you want to use the current settings for all the compatible gadgets in the dashboard. This option eases the pain of configuring one by one the rest of the gadgets with the same default configuration.

Integrations

  • dev

We are working on our growing catalog of , but drop us a line in case you want us to expedite a specific one, visit our .

Dashboards

This gadget appears in the following dashboard: (see Agile Dev monday.com dashboard).

See also

Confluence®, Jira®, Atlassian Bamboo®, Bitbucket®, Fisheye®, and Atlassian Crucible® are registered trademarks of Atlassian®
Copyright © 2005 - 2024 Appfire | All rights reserved. Appfire™, the 'Apps for makers™' slogan and Bob Swift Atlassian Apps™ are all trademarks of Appfire Technologies, LLC.