...
As you probably noticed, on the right of the issue list you can see a Planning Panel with statistics for the selected Sprint-Team. If the sprint had Sprint-Team already set, then a Team field will show it. If you defined multiple teams, you can select the one to examine, from the Team dropdown. If you wish, you can select an individual team member and display only their sprint assigned issues.
The planning panel displays the total planned work for a selected Sprint-Team assignment, at the right side of the screen. Thus you can observe different views of original work estimation compared to resource time assignment in the team (Potential Capacity vs. Planned Work) .
Note: If there is not team defined for the sprint, the left panel is shown empty, and displays a reminder that a sprint team needs to be defined first.
...
Team Planned Work - At the top of the section you can see the total planned work of the team you selected. That is, all team members combined planned work compared to the total team potential capacity. The color of the bar indicates whether the planned work amount is less (green), 90-100% (yellow), or excessive (red) compared to team capacity.
...
Tasks - calculate only values of issues of types such as tasks, bugs and other issue types in that same level.
Tasks + Sub-tasks - calculate all the above elements and their sub-tasks (the original estimation given in the sub-tasks will be addressed and populated).
Sub-tasks - calculate only sub-tasks (the original estimation given in the sub-tasks will be addressed and populated).
Smart Calculation - Tasks + Sub-tasks, however, if for sub-tasks having original estimate, parent task values are not calculated.
Tracking
...
Different views of total time tracking (Original estimation,Remaining estimation, Logged work) of team resources. (10 sec refresh intervals, updates the views with time tracking changes and assignees)
...
Team - Team overview of total time tracking of team resources per related sprint
...
Role - Team time tracking overview per role (defined in the Team Configuration of total capacity of team resources per related sprint
...
Resource - Time tracking overview per person on the specific sprint compared to its availability configured in the team
...
Issues - Time tracking overview of all sprint issues in one place
...
The Tracking mode is available for the current active sprint (it is not relevant for future sprints; for past sprint you can observe the actual achievements in the app reports). Tracking allows you to observe how the progress of current active sprint compared to the work planned for it, before it was started. Therefore, the tracking mode freezes the estimated work just as the print was launched as the reference for the sprint planning goal. The app ignores, therefore, “estimation” changes that were made in the active sprint after it was launched. This ensure honest progress report evaluation compared to the original planning goal.
Note - you are of course able to change estimations of time or story points after the sprint has started. The modified values will appear in the Estimate issue field in the Planning % tracking tab. However, since the app calculation is based on the original estimate, this may appear as discrepancy between the issue list and the planning chart.
Tracking shows progress for the selected sprint team, for roles, and for individual team members.
Tracking progress for time based effort
When tracking progress of the time-effort based active sprint, the app freezes the planning goals as the time estimation of the various issues. If an issue also has remaining time value, this parameter is used as the work estimation entering into the sprint. The remaining time value is also displayed for the Estimate field in the issue list.
For every entity (sprint team, role and individuals) tracking shows color coded Actual vs. Expected.
The Actual value of work completed is calculated by the sum of Time tracking hours logged in all relevant issues (for team, role or individual) since the sprint launch.
The Expected value is based on the days passed since the sprint was launched. It sums the working hours defined for the participants based on the sprint-team definitions. A ticker in the bar chart shows where this value is expected to be.
...
If the progress, compared to the expectation is too low, it is colored red. If it’s close (80% and above) it is colored yellow. If it meets or exceeds expectation it is green.
Tracking progress for story points
Tracking progress of the story point based active sprint, freezes the planning goals when the sprint is launched. .
The Actual value of work completed is calculated by the sum of story points belonging to completed issues (for team, role or individual) since the sprint launch.
The Expected value is based on the days passed since the sprint was launched. It sums the daily points defined for the participants based on the sprint-team definitions. The ticker shows where this value is expected to be.
...