Sizing and Estimates

Print this topicEmail this topicSave as PDF

Rally uses resources to provide status for your releases and iterations and help you ensure that your development remains on track. You can use these estimates to assist you in determining the velocity of your project and, as your team becomes better at estimating, predicting future velocity. Estimates are primarily totaled at the release and iteration level.

The following estimate increments are used in Rally:

  • Release units: The estimated amount of resources for a Release.
  • Iteration units: The estimated amount of resources for an Iteration.
  • Plan estimates: This estimate records the amount of effort estimated to complete the scheduled item.
  • Task estimates: This estimate records the amount of effort estimated to complete a Task.
  • To do: The amount of remaining effort required to complete a Task.

Most estimate units roll up into cumulative totals and can be viewed on the Iteration Status or Release Status views.

Rally setup initially defaults to the same units of measure (points) for both release and iteration units.

Estimates includes the following topics:

Use Rally Time Tracker to leverage Rally custom fields combined with the Custom Report Designer to generate customizable timesheet reports.

Actuals

Note: This field is hidden by default. It is recommended only to be used when retrospectives do not provide insight on root causes for missed commitments. It is not recommended to use this feature for time tracking to report on development cost. For that, see Rally Time Tracker.

The total hours spent on stories or defects including time on tasks associated with stories and defects, is represented by the Sum of Time Spent option. See Custom Reports for an example of how to run a report using Sum of Time Spent to see time spent working on a feature during a release.

Actuals reflect the actual amount effort a task took to complete. This figure is in contrast to the amount of effort that was originally estimated to complete the task. Actuals are entered on a task and rolled up (accumulated) to display on the parent user stories.

Actuals are measured in iteration units.

Using actuals from the Task Detail page, the actual figure is entered by the developer on the Task Detail page when the task is completed.

Using actuals from the Task Summary page:

  • The task actuals are displayed individually as well as totaled on the Task Summary page.
    • Individual task actuals are displayed in each task row.
    • Total task actuals are displayed in the shaded box in the header of the table.
  • Filter your tasks display to show a single release or iteration. The resulting actuals total applies only to the filtered view.

Using actuals from the Team Status page:

  • Actuals are displayed under the Actuals header.
  • Expand this page to view the actual amount of effort employed per:
    • Task
    • Individual team member
    • Entire team for the iteration

Using actuals from the Iterations Summary and Releases Summary views:

  • The actual amount is displayed under the Actual header.
  • You can view the cumulative amount of actuals for all tasks in the iteration or release.

Iteration units

Iteration units are configured when you create or edit a workspace. A label for your iteration units of the workspace is entered on the Units Configuration page. This label (Points, Days, Ideal Developer Weeks) identifies how your development will estimate resources available for any iteration.

Using iteration units from the Iteration Detail page, input the amount of iteration units. This figure represents the total available iteration resources.

Using iteration units from the Iteration Status page, use the blue Iteration Indicator box and click the Summary tab from the Resources section to show summary details.

Iteration resources, plan estimates, task estimates, and task to do are all measured in iteration units.

Plan estimates

Plan estimates record the amount of iteration units required to complete a work item. Plan estimates are entered on the work item and are rolled up (accumulated) from a child work item to the related parent work item. Work item estimates are rolled up and reflected on the Iteration Status page.

Plan estimates are measured in iteration units and are applied to a work item once it is scheduled.

Task estimates roll up and compare to the plan estimate.

Using plan estimates from the Iteration Status page, use the blue Iteration Indicator summary box in the upper-right of the page to view the plan estimates in relation to task and to do estimates.

Using plan estimates from the Iterations Summary and Releases Summary views:

  • The plan estimate amount is displayed under the Plan Est header.
  • Rally totals and displays the amount of plan estimates for all user stories scheduled into an individual iteration or release.

Planning units

Release and iteration planning units are configured when you create or edit a workspace. A qualifying label for your planning units is entered on the Units configuration page. This label (Points, Months, Weeks) identifies how your development will estimate resources available for any release or iteration.

Using planning units from the Release Detail page, as you define a release, input the number of planning units for the release. This figure represents the total available release resources.

Using planning units from the Iteration Detail page, as you define an iteration, input the number of planning units for the iteration. This figure represents the total available iteration resources.

Task estimates

Task estimates are entered for each task by the development team. This field records the number of units estimated to complete a single task. Task estimates are calculated in increments of task units defined by your administrator. Task estimates are measured in iteration units.

Using task estimates from the Task Detail page, enter the task estimate on the Task Detail page.

Using task estimates from the Task Summary page:

  • View the estimate for each task on the Task Summary page
  • The task estimates are displayed individually as well as totaled on the Task Summary page. The individual task estimate is displayed in each task row, and the cumulative task estimate total is displayed in the shaded box in the header of the table.

Using task estimates from the Iteration Status view:

  • This view displays the tasks assigned to a user story for a specified iteration.
  • The task estimate for each task displays on each task row of the expanded Iteration Status view.
  • The task estimates are totaled for each user story and displayed on each row of the related user story.
  • All task estimates for all user stories of the iteration are totaled and displayed in the Task Est field in the shaded box in the header of the table to help you assess the status of your iteration.
  • Use the summary view of the blue Iteration Indicator box in the upper center right of the page to view the task estimates in relation to plan and to do estimates.

Using task estimates from the Iterations Summary and Releases Summary views:

  • The task estimate amount is displayed under the task header.
  • Rally totals and displays the amount of task estimates for all tasks scheduled into an individual iteration or release.

To do estimates

To do estimates reflect the amount of effort remaining to complete a task. At each day's end, the developer updates the current amount of effort left to do on each task they have worked on so the entire team can remain informed of the status of all tasks. To do estimates are measured in iteration units.

Using to do estimates on the Task Detail page, the to do estimate is entered on the Task Detail page.

Using to do estimates on the Task Summary page:

  • A cumulative total for the amount of units remaining to do is displayed in the shaded box at the top of the page.
  • Filter your task view to display the current iteration. The resulting to do estimate totals apply only to the filtered view.

Using to do estimates on the Team Status page:

  • The to do amount is displayed under the To Do header.
  • Expand this page to view the amount of effort remaining by task, by individual team member, or by the entire team for the iteration.

Using to do estimates on the Iteration Status view, use the blue Iteration Indicator box in the upper-right of the page to view the to do estimates in relation to task and plan estimates.

Using to do estimates on the Iterations Summary and Releases Summary views:

  • The to do amount is displayed under the To Do header.
  • Rally totals and displays the amount of to do units for all work items scheduled into an individual iteration or release.
© 2012 Rally Software Development Corp | Legal