Create an Iteration
An iteration is a single, complete development timebox, usually 2-4 weeks in length. An iteration produces intermediate deployable code that has been discussed, designed, implemented, and tested. Each iteration is a subset of the final product under development and builds on the functionality of the prior iteration. The iterations grow incrementally to become the final system. A project can contain one or many iterations.
Creating an iteration includes:
Use the summary and detail pages
The Iteration summary page provides basic information regarding all iterations that have been created. When using a project hierarchy, this page reflects any view scoping settings that you have indicated in the project drop-down list box. All columns display the cumulative totals for all projects that have the same iteration name and time box (Start and End date).
Adding a new iteration from a Summary view returns you to the Summary page from which the iteration was created. Your new iteration is added to the end of your summary display, forcing you to scroll to this location unless you have applied filter or sort criteria.
From the Iteration summary page you can:
- Select the Edit icon to the right of each iteration to edit that iteration.
- Determine your current iteration. The current iteration is the one that contains today's date.
Use the Iteration summary page to find information about your iterations, such as:
- Iteration Velocity Chart: The Plan Estimate Units accepted per iteration for up to ten previous iterations.
- Planned Velocity: The amount of estimate units the team anticipates they can complete in the release.
- Plan Est: The roll-up of the gross-level estimates for all of the scheduled items assigned to the iteration.
- Task Est: The roll-up of the estimates for all of the tasks assigned to the iteration.
- To Do: The cumulative remaining amount of work units to be completed for all tasks in the displayed iteration.
- Actual: A roll-up from all tasks which accumulates the true time the tasks assigned to this iteration took to complete. This is helpful for estimating future tasks.
The Iteration detail page provides a view of an individual iteration.From the Iteration detail page, you can:
- View a read-only display of a single iteration in its entirety including all current field values and details.
- Perform multiple activities on the sidebar located on the left of the page. The sidebar displays any associated artifacts related to the current iteration. Use the show and hide icons to control the sidebar display.
- Click the URL icon in the upper-left corner of the detail page to open a New Iteration Detail page with the complete URL to this work item. From here you can copy the URL to use as a reference link in email to team members, or attachments to other work items, and so on.
- Use the Actions button to select options such as Edit, New, Copy, Print, Delete.
Create and edit an iteration
Your ability to create, edit, or view an iteration is dependent upon the user role and permissions you have been assigned for the project.
Bulk create iterations
If you use a project hierarchy, bulk create is available for use in managing your iterations. Bulk create allows you create a single iteration and propagate it to all child projects of your current project. This saves time spent in configuration and makes it easy to establish shared schedules across child projects.
In order to use the bulk create feature:
- You must be in a parent project to use the Bulk Create field.
- You can only create releases for those child projects for which you have create permissions.
When you use Bulk Create, the Release Name, Start Date, End Date, and State fields are automatically copied from the parent project iteration to the child project iteration.
Bulk update iterations
If you use a project hierarchy, you have the option of propagating edits made to the parent project to all related child projects using bulk update. Rally tracks all linked child projects and updates specified fields to keep the entire project hierarchy in synch.
- Select the Plan tab, then select Iterations.
- Select the iteration you wish to edit. From Actions, select Edit Iteration.
- On the Edit Iteration editor page, select one or both of the Bulk Actions checkboxes to publish your iteration to all linked child projects:
- Update matching iterations in all child projects
- Update Name and Release Date when changed in parent projects
- Complete the other fields on the editor as necessary.
- Click Save.
In order to use the bulk update feature:
- You must be in a parent project to use the Bulk Actions fields.
- You can only edit releases for those child projects for which you have update permissions.
When bulk update is activated, changes to the following fields are updated in the linked child projects:
- Start Date
- Release Date
When editing a child project, the State field can be individually edited, but as long as the child project is still linked to the parent project through the Bulk Update field, any bulk update to the parent project will overwrite the individual edits.
You can unlink individual child projects from the parent project Bulk Update by deselecting the Bulk Update field. When deselected, the Name, Start Date, and Release Date fields are enabled. Make a change to any of these fields and from this point on, the child project release is unlinked and is not updated when bulk updates are made from the parent project.
Delete an iteration
To delete an iteration, do the following:
- Navigate to the Plan → Iterations page.
- Click on the name of the iteration you want to remove.
- Under the Actions drop-down on the top right of the page, choose Delete.
Set these field values when creating or editing an iteration. Fields highlighted in red are required.
|Bulk Create||Select this checkbox to apply this iteration to all child projects. This checkbox displays when you are in a parent project and create a new iteration. The iteration is created using the same Name and End Date in all child projects of your current parent project.|
|Bulk Update||Select this checkbox to allow edits made to the parent project iteration to be replicated for all child projects iterations. Deselect from an individual child project iteration to remove its link from the parent project release and allow a unique edit or update to the child project iteration. This field displays only for an iteration that has the Bulk Create option enabled.|
|Name||Enter the name of the iteration.|
|Theme||Use this Rich Text Format field to enter a theme for your iteration.|
|Start Date||Click the icon and select the start date for the iteration of the software or application from the resulting calendar.|
|End Date||Click the icon and select the date which targets an iteration of the software or application from the resulting calendar.|
|State||Specify the current condition of the iteration. Valid values are:
|Planned Velocity||Specify the total number of points that the team thinks it can complete within this iteration. Although points is the recommended unit, you may customize the definition of units to indicate some other unit of measure.|
|Project||The current project for the iteration. The project field defaults to the project you are in and cannot be edited. To create an iteration in a different project, you must first switch to that project then create the iteration.|
|Plan Estimate, Task Estimate, Accepted, and To Do||These totals are rolled up from the estimates given for the associated scheduled items and their tasks along with the actual number of units of remaining work to be done. The Accepted field calculates and displays the total of scheduled item estimates whose state have been set to accepted. These figures are presented to assist you in providing more accurate estimates for future iterations. These fields are calculated in iteration units.|
|Notes||Record additional information associated with the iteration such as team decisions or discussion results.|
|Change Description||Record any changes made to the iteration during an edit. Comments are stored and displayed in the Revision History page. Note: Changes made to the iteration are also systematically captured for Revision History.|