See how your sprint is progressing, what work items are being worked on and by whom, your effort, tracked time for parent and child items, and pace
Iterations Page Columns and What They Mean
How to assign a budget to an iteration
How to assign a budget to a work item
Intro
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 Azure DevOps, 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?"
"Iterations" Page At-A-Glance
|
ID
|
Description
|
|---|---|
| 1 |
The list of all iterations from your DevOps project settings. |
| 2 |
The name of the iteration you currently have selected. |
| 3 |
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. |
| 4 |
Options to view the tracked time details of work items within an iteration:
Iteration Start Date + 1 day 00:00AM == midnight next day
|
| 5 |
Total time tracked for all work items from the selected iteration. Additionally, the total tracked time for work items in a completed state ( |
| 6 |
The Total Story Points (total effort) of all work items from the selected iteration. Additionally, you can view the total effort/story points for the work items in completed and incomplete state. Note: This field displays the total only if you configure the Pace Calculation option on the Settings -> Work Item Automation page. If this isn't configured, the Total Effort field displays the status as Inactive. |
| 7 |
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, click here. |
Iterations Page Columns
The following table details the columns found on the "Iterations" page.
|
Column
|
Description
|
|---|---|
|
ID |
The unique ID of the work item within DevOps Server/Services. |
|
Title |
The title of the task within DevOps Server/Services. |
|
Iteration Path |
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. |
|
State |
The current state of the work item. |
|
Effort |
The number of user story/complexity points (effort) estimated for the work item. |
|
Tracked |
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 tracked hours by estimated effort. |
|
Budget |
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. |
Assigning a Budget to an Iteration
Budgets are usually assigned to iterations or even whole releases. After you assign a budget to an iteration, you can go to the "Budgets" page, click on that budget, and verify that the iteration was added by looking in the Included section of the page. You can also view the list of included work items from that iteration. For more information about the "Budgets" page, see Budgets Page Overview.
1. On the 7pace Timetracker menu bar, click Iterations.
2. In the left pane, click the iteration name for which you want to assign a budget.
3. At the top-right corner of the web page, click the Budget dropdown.
The list of budgets created on the "Budgets" page displays.
4. From the dropdown list, select the budget that you want to assign to the selected iteration.
The entire iteration is assigned to that budget.
Assigning a Budget to a Work Item
If you only want to bill a customer for certain work items in an iteration, you can simply exclude those unbillable work items from one budget by assigning them to a different one. You can do this on the "Iterations" page by clicking on the "Budget" column dropdown arrow next to each work item row (see more details, below). These work items will display in the Excluded section of that budget on the "Budgets" page. For more information on changing work item on budgets, see how to include work items in a budget and how to exclude work items from a budget.
Please note that budgets are inherited. A budget that is assigned to a parent object will be used by all child objects as long as no other budget is assigned. When you assign a different budget to child items, they are considered exceptions to the inherited budget settings.
For example, if you assigned a budget to the whole release (Budget "A"), but you assign a different budget (Budget "B") to a product backlog item (PBI), somewhere deep inside this release (e.g. in release\iteration\parent PBI\child PBI), all time that has been recorded on that PBI or to its child items will then be counted in Budget "B".
Important: The budget inheritance from a parent work item to child work items overrides the budget inheritance from an iteration to its work items.
1. In the left pane of the "Iterations" page, click the iteration name.
2. Highlight the row of the specific work item you want to assign to a different budget than that of the entire iteration. When you hover over the row with your mouse, the row will be highlighted in blue.
3. In the Budget column of the highlighted row, click the row corresponding to the work item.
4. From the drop-down list, select the budget that you want to assign to the work item.
The work item is automatically assigned to the new budget. If you now go to the "Budget" page of Timetracker, you will see that work item in the "Excluded" section of the budget from which you removed it.
Related Articles
Comments
0 comments
Please sign in to leave a comment.