Agile Manager widget descriptions This document provides details about commonly used Agile Manager dashboard widgets. Note: All widgets in the Dashboard are configurable, and the following descriptions cover the default displays only. To configure a widget, click the dropdown arrow in the widget header, and select Configure Settings. In the following descriptions, refers to how often the data is calculated, and not neccesarily how the data is displayed. Team Velocity Velocity (columns) Average Velocity (line) For a given release and team: The number of story points completed by the team in the past and current sprints of the given release, compared with the average number of story points completed in past sprints of the given The number of story points completed in a sprint, and within 4 days after the sprint end date. Takes into account all past sprints in the It does not take into account the story points closed in the current sprint. in the release Group Velocity Velocity (columns) Average Velocity (line) For a given release and team: The number of story points completed by all teams in the past and current sprints of the given release, compared with the average number of story points completed in past sprints of the current The number of story points completed in a sprint, and within 4 days after the sprint end date. Takes into account all past sprints in the It does not take into account the story points closed in the current sprint. 1
Release Burn Up Displays the progress towards completing the release plan. The graph compares the number of story points completed at any point on the release timeline, with the number of story points planned for the same point in time. Story Points The total number of story points planned for the release at the end of any day in the 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 given day. Done Story Points (X-Axis) The total number of release story points that are marked as Done at the end of any given day during the Calendar days in the The origin represents the beginning of the first day of the Sprint Burn Up Sprint scope 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. The total number of hours estimated for the tasks at the end of any given 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 given day. Invested effort The total number of hours invested in sprint tasks at the end of any given day in the sprint. Calendar days in the sprint. The origin represents the beginning of the first day of the sprint. 2
Release Burn Down Remaining Story Points (curve) Expected Velocity (diagonal line) The remaining open story points for all teams, on any given day in the release, compared with where the teams should be, based on the expected velocity. The number of story points associated with all open user stories and defects assigned to the release, at the end of any given day in the A guide as to the amount of open story points that should remain for all teams, on any given day in the 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 is zero. The diagonal line connects these two points. Note: If a team s expected velocity is changed during a release, the new expected velocity is adjusted from the beginning of the release timeline. (*) Each team s expected sprint velocity can be found in the configuration area, on the Release > Teams > team details configuration page, under Est. Sprint Velocity. Calendar days in the The origin represents the beginning of the first day of the Sprint Burn Down Remaining Effort (curve) Capacity (diagonal line) The team s remaining work hours at the end of any given day in the sprint, compared with where the team should be, based on the team s calculated capacity. The number of work hours associated with open tasks at the end of any given day in the sprint. A guide as to the amount of work that should remain for the team on any given 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). Note: If a member s capacity is changed during a sprint, the new team expected capacity is adjusted from the beginning of the sprint timeline. Calendar days in the sprint. 3
The origin represents the beginning of the first day of the sprint. Release Backlog Cumulative Flow Diagram Displays the number of backlog items in each status at any given time in the Looking vertically, you can see the distribution of backlog items across different statuses at any point in the Looking horizontally, you can track the progression of statuses along the release timeline. Calendar days in the The origin represents the end of the first day of the Team Workload Remaining Work within Capacity (blue bar) Remaining Free Capacity (white bar) Remaining Work Over Capacity (red bar) The number of work hours remaining for each team member until the end of the sprint. The number of work hours associated with open tasks in the sprint, and assigned to the team member. 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. The number of work hours assigned to the member that exceeds the team member s capacity. 4
Release vs Actual Backlog Items Backlog items that were assigned to sprints before or within two days of the beginning of each sprint. The column aggregates planned items for all the release sprints, and groups them by done and not done items. Backlog items that were assigned to sprints later than two days from the beginning of each sprint. The column aggregates added items for all the release sprints, and groups them by done and not done items. Release vs Actual Backlog Items (by Story Points) Backlog items that were assigned to sprints before or within two days of the beginning of each sprint. The 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. Backlog items that were assigned to sprints later than two days from the beginning of each sprint. The 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. Sprint vs Actual Backlog Items 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 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. Sprint vs Actual Backlog Items (by Story Points) 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. 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. 5