Page Comparison

...

Excerpt
hidden true
XXXDisplay the number of resolved issues during a given period of time

Overview

Track the total work remaining and project the likelihood of achieving the sprint goal. This helps your team manage its progress and respond accordingly.

A burndown chart shows the amount of work that has been completed in an epic or sprint, and the total work remaining. Burndown charts are used to predict your team's likelihood of completing their work in the time available. They're also great for keeping the team aware of any scope creep that occurs. 

Burndown charts are useful because they provide insight into how the team works. For example:

• If you notice that the team consistently finishes work early, this might be a sign that they aren't committing to enough work during sprint planning. 

• If they consistently miss their forecast, this might be a sign that they've committed to too much work.

• If the burndown chart shows a sharp drop during the sprint, this might be a sign that work has not been estimated accurately, or broken down properly.

This report shows the amount of work to be done in a sprint. It can be used to track the total work remaining in the sprint, and to project the likelihood of achieving the sprint goal. By tracking the remaining work throughout the sprint, a team can manage its progress, and respond to trends accordingly. For example, if the burndown chart shows that the team may not reach the sprint goal, then they can take the necessary actions to stay on track.

This gadget displays all the pending impediments or blockers of a sprint. For an issue to be identified as an impediment or blocker, it has to meet any of the following criteria:

• The issue is flagged as important. These issues are displayed in yellow and with the flag icon (see Jira cloud flag an issue).

• The issue has a link “blocks” to other issue, which in turn is linked with a “blocked by” relationship to the blocker issue.

Some users identify blockers by other means like using a workflow state “blocker” and a column “blocked”, with labels or with a priority “blocker”. However, none of these methods are taking into account because they are unusual.

...

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.

This gadget displays:

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

• In the vertical axis (y axis) the unit of measurement chose to estimate the work: Story points, original time estimate or issue count.

• A grey line. This line is a guide for your team to approximate where they should be, provided the work was done in a linear progress. The ideal amount of work left.

• Green bars. Each bar indicates the amount of work done in that day.

• A blue line. This line is the real amount of work left, based on the unit to estimate the work (story points, original time estimate or issue count).

...

Configuration

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

• The datasource, where Current indicates the Jira cloud instance where the app is installed.

• The project and the board where the issues are located. By default, all the issues are displayed, no matter the active sprint they belong to, in case there are parallel sprints.

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

  • Story points. Your team will burn down the story points estimations they did in the backlog.

  • Original time estimate. Your team will burn down the time estimations they did in the backlog i.e., duration of the issues in hours or days in the Original Estimate field.

  • Issue count. Your team will burn down the number of issues completed. 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

• (see Jira Software cloud)

...