The "Iterations" page of 7pace Timetracker provides you with a quick snapshot of how your sprint is progressing. Here, you can view the tracked time details of work items according to the specific iterations to which they belong. Featuring a sprint-oriented view of the time spent by your team, the "Iterations" page is similar to the look and feel of the "Backlog" page of TFS, but with more robust information. The "Iterations" page allows you to assign budgets to whole releases or single work items and provides you with a unique window into the following:
- "How is the sprint running?"
- "What work items are currently being worked on and by whom?"
- "Which work items were moved to a different iteration?"
- "What is progressing well in the sprint and what requires our attention?"
- "How accurate were our team's estimations?"
- "What is the team's pace on particular work items or the sprint as a whole?"
The list of all iterations from your Team project settings.
|2||The name of the iteration you currently have selected.|
The timeframe or date range of the current iteration.
The date range appears only if you have configured it for the iteration. Otherwise, "No Iteration Dates" displays.
Options to view the tracked time details of work items within an iteration:
Total time tracked for all work items from the selected iteration.
Additionally, the total tracked time for work items in a completed state () and work items in an incomplete state () is also displayed.
The Total Story Points (total effort) of all work items from the selected iteration.
Additionally, you can separately view the total effort/story points for the work items in completed state and work items in incomplete state.
Note: This field displays the total only if you configure the Pace Calculation option on the Configuration page. If you do not configure this option, the Total Effort field displays the status as Inactive. For more information, see "Settings": Work Item Settings.
The budget inherited from the parent item or specifically assigned to the iteration.
If there is no budget assigned to the iteration, this field displays None. For more information about assigning budget to an iteration, see "Iterations" Page: Assigning a Budget to an Iteration.
Iterations Page Columns
The following table details the columns found on the "Iterations" page.
|ID||The unique ID of the work item within Team Services.|
|Title||The title of the task within Team Services.|
The path of the iteration.
Note: This column also displays the new iteration path for work items that are moved from the selected iteration.
|Assigned To||The name of the person to whom the work item is assigned.|
The current state of the work item.
|Effort||The number of user story/complexity points (effort) estimated for the work item.|
The total time tracked for the corresponding work item.
There are two states - tracked within last 2 hours and 48 hours. Hover your mouse over your entry to see the state of the work item:
Tracked within the last two (2) hours:
Tracked within 48 hours:
|Tracked Summary||The total tracked time for the parent work item and all its child work items.|
|Pace||The pace at which the task is performed. This number is calculated by dividing the number of hours by estimated effort.|
Displays the current budget assigned to the work item.
Budgets are usually assigned to iterations or even whole releases. However, if you don't want to bill a customer for certain work items in a sprint/iteration, you can simply exclude them from one budget (e.g. "Company X Billable") and move them to a different budget instead (e.g. "Company X Non-Billable") by clicking on the "Budget" column dropdown arrow next to each work item row.