Displays user stories assigned to you or created by you, depending on widget configuration.

If the widget is configured to display stories assigned to you, it also includes stories with tasks assigned to you, even if the story itself is assigned to another user.

This widget does not display user stories with a status of Done.

Displays defects assigned to you or created by you, depending on widget configuration.

If the widget is configured to display defects assigned to you, it also includes defects with tasks assigned to you, even if the defect itself is assigned to another user.

Displays items in the release that are currently blocked.

Description

The number of work hours remaining for each team member until the end of the sprint.

Remaining Work within Capacity (blue bar)

The number of work hours associated with open tasks in the sprint, and assigned to the team member.

Remaining Free Capacity (white bar)

The amount of free capacity the team member has remaining.

At the bottom of the widget, the number of Hours of unassigned tasks refers to hours of tasks that are assigned to the sprint, but not assigned to any team member.

Remaining Work—Over Capacity (red bar)

The number of work hours assigned to the member that exceeds capacity.

Description

Displays the number of backlog items in each status at any specified time in the release.

• Looking vertically, you can see the distribution of backlog items across different statuses at any point in the release.
• Looking horizontally, you can track the progression of statuses along the release timeline.

Time Scale

Work days in the release.

Each point on the X-Axis represents the end of the indicated day, and Y-Axis values are the values for the end of that day.

The origin represents the end of the first day of the release.

Frequency

Daily

• Click on legend items to add or remove content from the graph.
• Hover over spots in the graph to view more data.

Description

For a specific release and team: The number of story points completed by the team in the past and current sprints of the specified release, compared with the average number of story points completed in past sprints of the specified release.

Velocity (columns)

The number of story points completed in a sprint, and within 7 days after the sprint end date.

Average Velocity (line)

Takes into account all past sprints in the release. It does not take into account the story points closed in the current sprint.

Time Scale

Sprints in the release

Frequency

Sprints

Description

For a specific release and team: The number of story points completed by all teams in the past and current sprints of the specified release, compared with the average number of story points completed in past sprints of the current release.

Velocity (columns)

The number of story points in a sprint, and within 7 days after the sprint end date.

Average Velocity (line)

Takes into account all past sprints in the release. It does not take into account the story points closed in the current sprint.

Time Scale (X-Axis)

Sprints in the release

Frequency

Sprints

Description

For a specified release, sprint, and team: The cycle times of backlog items delivered in the sprint.

The graph indicates the items' cycle times relative to the average cycle time.

Click individual items in the graph to display additional data in a tooltip.

Days (Y-Axis)

The total number of days in an item's cycle time.

Time Scale (X-Axis)

Work days in the sprint, indicating the date on which the item was marked as Done.

Description

For a specified release and team: The cycle times of backlog items delivered in the release.

The graph indicates the items' cycle times relative to the average cycle time.

Click individual items in the graph to display additional data in a tooltip.

Days (Y-Axis)

The total number of days in an item's cycle time.

Time Scale (X-Axis)

Work days in the sprint, indicating the date on which the item was marked as Done.

Description

Displays the progress towards completing the sprint plan. The graph compares the number of hours invested so far in the sprint, with the total number of hours assigned to the tasks planned for the sprint.

Sprint scope

The total number of hours estimated for the tasks at the end of any specific day in the sprint.

The value can change as tasks are added to– or removed from– the sprint plan.

Changes in scope are highlighted by vertical lines in the graph, indicating additional items planned on the specified day.

Invested effort

The total number of hours invested in sprint tasks at the end of any specific day of the sprint.

Time Scale

Work days in the sprint.

Each point on the X-Axis represents the end of the indicated day, and Y-Axis values are the values for the end of that day.

The origin represents the beginning of the first day of the sprint.

Frequency

Daily

• Click on legend items to add or remove content from the graph.
• Hover over spots in the graph to view more data.

Description

The team’s remaining work hours on any specific day in the sprint, compared with where the team should be, based on the team’s calculated capacity.

Remaining Effort (curve)

The number of work hours associated with open tasks in the sprint.

Capacity (diagonal line)

A guide as to the amount of work that should remain for the team by a specified day in the sprint. On the start of the first day of the sprint, the team capacity (remaining work effort in hours) is equal to the sum of each member’s capacity for the sprint.

Each member’s capacity for the sprint is equal to the member’s work hours per day, multiplied by the number of work days for the team member in the sprint. This value is found in the team member planning buckets on the right side of the Sprint Backlog page (Release Management > Sprint Backlog).

Time Scale

Work days in the sprint.

Each point on the X-Axis represents the end of the indicated day, and Y-Axis values are the values for the end of that day.

The origin represents the beginning of the first day of the sprint.

Frequency

Daily

• Click on legend items to add or remove content from the graph.
• Hover over spots in the graph to view more data.

Description

Displays the progress towards completing the release plan.

The graph compares the number of story points at any point on the release timeline, with the number of planned story points at the same point in time.

Story Points

The total number of story points planned for the release.

The value can change as story points are added to– or removed from– the release plan.

Changes in scope are highlighted by vertical lines in the graph, indicating additional items planned on the specified day.

Done Story Points

The total number of release story points that are marked as ‘Done’ at the end of any specific day during the release.

Time Scale (X-Axis)

Work days in the release.

Each point on the X-Axis represents the end of the indicated day, and Y-Axis values are the values for the end of that day.

The origin represents the beginning of the first day of the release.

Frequency

Daily

• Click on legend items to add or remove content from the graph.
• Hover over spots in the graph to view more data.

Description

The remaining open story points for all teams, on any specific day in the release, compared with where the teams should be, based on the expected velocity.

Remaining Story Points (curve)

The number of story points associated with all open user stories and defects assigned to the release, by the end of any specific day in the release.

Expected Velocity (diagonal line)

A guide as to the amount of work (open story points) that should remain for all teams, by a specified day in the release.

At the start of the first day of the release, the teams’ expected velocity is the sum of all teams’ expected sprint velocities*, multiplied by the number of sprints. At the end of the last day of the release, the expected velocity (remaining work) is zero. The diagonal line connects these two points.

(*) Each team’s expected sprint velocity can be found in the configuration area, on the team details configuration page, under Est. Sprint Velocity. For details, see Configure team settings.

Time Scale

Work days in the release.

Each point on the X-Axis represents the end of the indicated day, and Y-Axis values are the values for the end of that day.

The origin represents the beginning of the first day of the release.

Frequency

Daily

• Click on legend items to add or remove content from the graph.

• Hover over spots in the graph to view more data.

Planned

Backlog items that were assigned to the sprint before– or within two days of– the beginning of the sprint. Backlog items are grouped by done and not done items.

Added

Backlog items that were assigned to the sprint later than two days from the beginning of the sprint. Backlog items are grouped by done and not done items.

Planned

Backlog items that were assigned to the sprint before– or within two days of– the beginning of the sprint. Backlog items are grouped by done and not done items. Backlog items are expressed here in terms of story points.

Added

Backlog items that were assigned to the sprint later than two days from the beginning of the sprint. Backlog items are grouped by done and not done items. Backlog items are expressed here in terms of story points.

Planned

Backlog items that were assigned to sprints before– or within two days of– the beginning of each sprint. Each column aggregates planned items for all the release sprints, and groups them by done and not done items.

Added

Backlog items that were assigned to sprints later than two days from the beginning of each sprint. Each column aggregates added items for all the release sprints, and groups them by done and not done items.

Planned

Backlog items that were assigned to sprints before– or within two days of– the beginning of each sprint. Each column aggregates planned items for all the release sprints, and groups them by done and not done items. Backlog items are expressed here in terms of story points.

Added

Backlog items that were assigned to sprints later than two days from the beginning of each sprint. Each column aggregates added items for all the release sprints, and groups them by done and not done items. Backlog items are expressed here in terms of story points.

Displays the forecasted progress until all release content is completed, as well as the release progress so far, for the selected release and team(s).

The total number of story points estimated for the release's backlog items at the end of any specified day in the release.

The value can change as items are added to– or removed from– the release plan.

Changes in scope are highlighted by diagonal lines in the graph, indicating additional items planned on the specified day.

Planned Velocity (light purple line)

A guide as to the amount of work that should be completed for all teams, by a specified day in the release.

This line is based on the Expected Velocities for all teams in the sprints.

Done (green line)

Backlog items marked as Done by the current date.

Forecast (dotted line):

• green if release is ahead
• red if release is in delay

The forecasted progress until the teams complete the currently planned content, based on the settings configured.

This line is based on the average story points per day, and can change as user stories or defects are added to– or removed from– the sprint plan.

• Select a time period for the report. This determines the data on which the calculation is based.

  You may want to ignore the first sprints or only use the last 10 days, because the expectation is that you improve and stabilize your delivery over time.

• Select the teams to include in the report. This also affects the average number of story points.

  For example, if a specific team did not contribute to the sprints included in the report, exclude the team from the report.

Marks the scheduled end of the release.

Time Scale

Work days and sprints in the release.

Each point on the X-Axis represents the end of the indicated day or sprint, and Y-Axis values are the values for the end of that day or sprint.

The origin represents the beginning of the first day of the release.

Frequency

Daily

• Click on legend items to add or remove content from the graph.
• Hover over spots in the graph to view more details.