Follow
Creating an Iteration

Iterations are a key component for Scrum agile teams in planning out work capacity. Workfront allows Scrum agile teams to manage their work by creating multiple iterations to accommodate team needs.

Creating an Iteration

  1. Navigate to the People area in the Global Navigation Bar.
  2. Ensure that the Teams tab is selected, then select the agile team from the drop-down menu.
    agile_iteration_create.png
    If you do not have an agile team, you can create one, as described in "Creating Agile Teams."
  3. Click the Backlog tab, then click Plan Iteration.
    agile_iteration_plan.png
  4. Specify the following information:
    Iteration Name: Specify a name for the iteration.
    Start Date: Specify the date the iteration should start. 
    End Date: Specify the date the iteration should end.
    When setting the end date, select a working day as the end date for the iteration, because the burndown chart uses only working days when calculating the burndown.
    By default, the burndown chart uses the default schedule to define working days (as described in "Creating Default Schedules"). Or, to incorporate team-specific non-working days, agile teams can choose to use an alternate schedule (as described in"Defining an Alternate Team Schedule for Burndown Charts" in "Creating and Managing Agile Teams").
    Focus: Specify the focus percentage of the team. If all members of the team will be focused completely on this iteration, the focus would be 100%.
    Workfront pre-populates this field with the average value from your team's past iterations. If this is your team's first iteration, this field value is 0 by default.
    Capacity: Specify the capacity for the iteration. This is the number of points or hours your team is able to accomplish in the iteration. The number you enter must be equal to or greater than the number of points or hours from the sum of all the stories in the iteration. 
    Workfront pre-populates this field with the average value from your team's past iterations. If this is your team's first iteration, this field value is 0 by default.
    Goal: Specify a goal for the iteration. This field is not required.
  5. (Optional) Select stories to add them to the iteration now, or you can skip this step and add stories to an iteration at a later time. The stories at the top of the backlog are higher priority. Stories are highlighted in green when they fit in the capacity; they are highlighted in red if they do not. 
    You can add both tasks and issues to a single iteration:
    • To add tasks to the iteration: On the Backlog tab, ensure that the Stories tab is selected (this tab is selected by default when viewing the backlog). Select the stories you want to add to the iteration.
      When you add tasks to an iteration, the start date of the task is calculated as described in "Understanding How Task Start Dates Are Calculate When Added to an Iteration."
    • To add issues to the iteration: On the Backlog tab, click the Issues tab. Select the issues you want to add to the iteration.
  6. Click Save.
    The iteration is created.
  7. (Optional) To add stories to an existing iteration, see "Adding Stories to an Existing Iteration" in "Creating and Managing Agile Iterations."

Understanding How Task Start Dates Are Calculated When Added to an Iteration

When you add a task as a story to an iteration, the Must Finish On task constraint is used for each story. In most cases, the planned start date of the task is calculated based on the following formula:

Iteration End Date minus (-) Task Duration equals (=) Task Planned Start Date

The Project End Date is used instead of the Iteration End Date if the project start date is after the iteration start date, and the project end date is after the iteration end date.

Setting a task's Planned Completion Date when it is added to the iteration:

-Project End Date is used when the project start date is after the iteration start date, and the project end date is after the iteration end date. Otherwise, the Iteration End Date is used.

Setting a task's Planned Start Date when it is added to the iteration:

-Iteration Start Date is used when the iteration start date is after the project start date.

Understanding How Iterations Are Referenced in the My Work Area

If a work item in the My Work area is a story on an iteration, the iteration name is displayed on the list instead of the project name.

For more information about using the My Work area, see "My Work."

 

This article last updated on 2018-02-28 22:24:59 UTC