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.

Scrum masters, product owners, and other organizers create iterations and modify their fields. Generally, teams create the next series of future iterations, to represent the team cadence, and serve as place holders for and discussion. During the Iteration Planning meeting, the entire team commits to a plan of work to be executed in an upcoming iteration.

Create and edit iterations includes:

Manage Iterations

Organizers can create, edit, and delete iterations from the Timeboxes page.

Your ability to create, edit, or view an iteration is dependent upon the user role and permissions you have been assigned for the project .

Use the Timeboxes page to find information about your iterations, such as:

  • Planned Velocity : The amount of estimate units the team anticipates they can complete in the release .
  • 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.

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 Name, Start Date, End Date, and State fields are automatically copied from the parent project iteration to the child project iteration.

Note: You cannot create another iteration in the same project with both the same start and end dates.

Follow these steps:
  1. Select the Plan tab, then select Timeboxes.
  2. Select Iterations from the Type drop-down.
  3. Select Add New, and enter the name, start, and end dates.
  4. Select Add with Details.
  5. On the Create New Iteration editor page, select the Bulk Actions checkbox to publish your iteration to all child projects.
  6. Complete the other fields in the editor as necessary.
  7. Select Save.

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. CA Agile Central tracks all linked child projects and updates specified fields to keep the entire project hierarchy in synch.

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:

  • Name
  • Start Date
  • Release Date
  • State

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 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.

Follow these steps:
  1. Select PlanTimeboxes.
  2. Select the iteration you wish to edit. From the gear menu, select Edit.
  3. In the Edit Iteration window, 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
  4. Complete the other fields on the editor as necessary.
  5. Select Save.

Delete an Iteration

Important:There is no recovery or revision history for deleted iterations. If you delete an iteration that stories and defects are scheduled in, they will all be updated to Unscheduled.
Follow these steps:
  1. Select Plan, Timeboxes.
  2. Select the gear icon next to the iteration you want to remove, and select Delete.

Iteration Fields

Set these field values when creating or editing an iteration. Fields highlighted in red are required.

Field Description
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 Select the calendar icon and select the start date for the iteration of the software or application from the resulting calendar.
End Date Select the calendar 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:
  • Planning: The iteration is not yet active and is still being planned for future activity.
  • Committed: The team has committed to the proposed set of work and is ready to begin the iteration. An iteration should be committed to before its start date.
  • Accepted: The team has met the iteration criteria.
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.


Need more help? The CA Agile Central Community is your one-stop shop for self-service and support. To submit feedback or cases to CA Agile Central Support, find answers, and collaborate with others, please join us in the CA Agile Central Community.