***

Iterations use story boards and burndown charts to visually represent how stories (tasks that are assigned to an agile team) are progressing during a fixed time-frame.

Multiple iterations can exist for an agile team, and the time-frame of iterations can overlap. For information about how to manage an agile team, see "Creating and Managing Agile Teams."

Iterations can contain custom data, be included in views, and can be reported on.

• Understanding Agile Iterations
• Creating and Accessing Iterations
• Adding Stories to an Existing Iteration

Understanding Agile Iterations

Agile iterations consist of three areas: completion status, burndown, and the story board.

For information about the burndown chart and completion status, see "Using the Agile Burndown Chart."

For more information about the story board, see "Using the Scrum Agile Story Board."

Creating and Accessing Iterations

• Creating a New Iteration
• Viewing Iterations
• Deleting an Iteration

Creating a New Iteration

Any team member with a Plan or Work license can create an iteration.

For information about how to create an iteration, see "Creating an Iteration."

Viewing Iterations

You can view all iterations for a given team, or you can view an individual iteration.

Iterations display data about the stories, issues, and documents that are contained in the iteration.

To view iterations assigned to a given team.

1. Click People in the Global Navigation Bar.
2. Click the Teams tab, then use the drop-down menu to select the team whose iterations you want to view.
3. Click the Iterations tab, then click All Iterations.
   By default, iterations are grouped by Current, Future, and Past.
4. (Optional) Click the name of the specific iteration that you want to view.
   The iteration stories are displayed. Find the link for this article-- For more information about working with the iteration, see Managing an Iteration.
   

Deleting an Iteration

1. Click People in the Global Navigation Bar.
2. Click the Teams tab, then use the drop-down menu to select the team whose iterations you want to view.
3. Click the Iterations tab, then click All Iterations.
   By default, iterations are grouped by Current, Future, and Past.
4. Select the iteration that you want to delete, then click Delete.

Adding Stories to an Existing Iteration

• Understanding When You Can Add Stories to an Iteration
• Understanding How Adding Stories Affects Task Dates
• Adding a Story to an Existing Iteration

Understanding When You Can Add Stories to an Iteration

You can add stories to an iteration in any of the following ways:

• While creating the iteration, as described in "Creating an Iteration"
• From the backlog after the iteration is created, as described in "Moving Stories from the Backlog to an Iteration or Kanban Board" in "Managing the Agile Backlog"
• From the Details page of the individual task or issue, as described in this section
• From a task or issue list
• From a report
• From a dashboard

Understanding How Adding Stories Affects Task Dates

When you add an existing task to an iteration, the task's Planned Start Date and Planned Completion Date are set as follows:

Task Planned Start Date

• The task uses the iteration's Start Date when:
  • The project does not have a Planned Start Date set.
  • The project's Planned Start Date is before or on the iteration's start date.
• The task uses the project's Planned Start Date when:
  • The project's Planned Start Date is after the iteration's start date.

Task Planned Completion Date

• The task uses the iteration's End Date when:
  • The project does not have a Planned Completion Date set.
  • The project's Planned Start Date is before or on the iteration's Start Date or the Project's Planned Completion Date is before or on the iteration's End Date.
• The task uses the project's Planned Completion Date when:
  • The project's Planned Start Date is after the iteration's Start Date and the project's Planned Completion Date is after the iteration's End Date.

Adding a Story to an Existing Iteration

You can add stories directly to an iteration.

IMPORTANT After the task moves to the iteration, you cannot update the Duration Type or Task Constraint. Duration Type is set to Simple and Task Constraint is set to Fixed Dates to keep the task timeline consistent with the iteration's timeline

From the tasks or issues tab

You can add any task or issue to any iteration if have Manage access to the project. Keep the following in mind when moving a task or issue to an iteration:

• If the task or issue is assigned to an agile team and moved to another team's iteration, the team assignment does not change.
• If the task or issue is not assigned to a team, the task or issue is assigned to the team who owns the iteration.

1. Navigate to the project, report, or dashboard that contains the task or issue you want to add to an iteration.
2. Select one or more tasks or issues.
3. Click More > Add to > Iteration.
   You cannot assign tasks or issues assigned to non-agile teams.
   
4. In the Add Stories dialog box, type the name of the iteration.
   NOTE You can move a story from an existing iteration to a new iteration. 
5. If you are adding tasks, click Add Stories.
   OR
   If you are adding issues, click Add Issues.

From a task or issue

You can add tasks only to iterations your team is assigned.

1. Navigate to the task or issue that you want to add to an agile iteration.
2. Ensure that the task or issue is assigned to the agile team.
3. Click the name of the task or issue to navigate to the details page.
4. Click Task Actions, then click Add to Iteration.
   Or
   Click Issue Actions, then click Add to Iteration.
   
5. In the Move Story dialog box, in the Select Iteration field, select the iteration where you want to move the task or issue.
6. Click Move Story.

***

Linked to Managing User Allocations.