Follow
Creating and Managing Agile Teams

Agile teams complete the work on iterations. A team needs to be identified as agile in Workfront in order to give the team an area for a backlog and iterations.

Creating an Agile Team from Scratch

  1. Navigate to the People area, then click the Teams tab. 
  2. Click the drop-down arrow next to the team name that is currently selected, then click Create New Team at the bottom of the drop-down list.
    The New Team dialog box is displayed.
  3. Specify the following information:
    Team Name: Specify a name for the new agile team.
    This is an Agile Team: Select this option to configure this new team to be an agile team.
    Team Members: Begin typing the name of a user to be on the team, then select the name when it appears in the drop-down list. 
    Repeat this process to add multiple users to the team.
    Description: Specify a description for the team.
  4. Click Create Team.
  5. Continue with "Managing an Agile Team."

Converting an Existing Team into an Agile Team

You can convert an existing team to be an agile team:

  1. Navigate to the 'People' area, then click the 'Teams' tab.
  2. Click the drop-down arrow next to the team name that is currently selected.
  3. Select the team that you want to convert to an agile team.
  4. Click the Team Settings link in the upper-right corner of the Teams tab.​ 
  5. In the 'Agile' section, select 'This is an Agile Team.'
  6. Click Save Changes.
  7. Continue with "Managing an Agile Team."

Managing an Agile Team

[! The information in the following steps is more or less duplicated in "Managing a Project in an Agile View."]

Configuring Whether Stories Are Estimated in Points or Hours

NOTE: This setting cannot be changed if the team has any iterations that are currently In Progress.

You can configure stories to be estimated either using points or hours.

To configure how stories are estimated for your agile team:

  1. Navigate to the People area, then click the Teams tab. 
  2. Select the agile team that you want to manage. 
  3. Click on the Team Settings link in the top right corner.​ 
  4. In the Agile section, in the Estimate Stories in area, select whether you want to use points or hours for estimating the size (work load) of stories. If you select Points, specify how many hours are equal to 1 point. (The default is 1 point = 8 hours.) This is the number of Planned Hours that are added to the story. For example, if you have selected to estimate stories in points and 1 point equals 8 hours, and a story is estimated at 3 points, 24 Planned Hours are added to the story.
  5. Click Save Changes.

Using an Alternate Team Schedule for Burndown Charts

Schedules that are defined in Workfront affect the burndown chart by excluding days off (weekends and holidays) from the burndown. 

By default, the burndown chart uses the default schedule. In addition to the default schedule, agile teams can choose to also use an alternate schedule in order to incorporate team-specific non-working days. This alternate schedule is then reflected in the burndown chart of any iteration that is assigned to the team. The alternate schedule affects only the burndown chart. (For more information about the default schedule, as well as how the Workfront administrator can create a team-specific schedule, see "Creating Default Schedules.")

The burndown chart does not take partial days into consideration. For example, if your team works 4 hours each Friday, it’s represented as a full day in the burndown chart.

For more information about using the burndown chart, see "Understanding the Burndown Chart" in "Creating and Managing Agile Iterations."

To use an alternate team schedule for burndown charts:

  1. Ensure that the Workfront administrator has already created the alternate schedule, as described in "Creating Default Schedules."
  2. Navigate to the People area, then click the Teams tab.
  3. Select the agile team that you want to manage. 
  4. Click on the Team Settings link in the top right corner.​ 
  5. In the Agile section, in the Schedule area, select the new schedule from the drop-down list.
  6. Click Save Changes.

Configuring Status Columns on the Agile Story Board

You can define the statuses that exist on the story board for the agile team. These are the statuses that are displayed on the story board as stories progress through the iteration.

To define the statuses that are available for each iteration associated with the agile team:

  1. Navigate to the 'People' area, then click the 'Teams' tab. 
  2. Select the agile team that you want to manage. 
  3. Click on the Team Settings link in the top right corner.​ 
  4. In the Agile section, in the Story Board area, select the columns that you want to show on the story board for each iteration associated with this team.
    Only system-wide statuses are available to select; you cannot select group-specific statuses.
  5. Click Save Changes.

Configuring Additional Fields to Display on Story Cards on the Agile Story Board

When you add fields to story cards, fields are view-only and display only when the field is populated.

By default, the following types of data is displayed on the story card:

  • Story name with a link directly to the task

  • The project name with a link directly to the project
    This link is displayed only for stories, not for subtasks

  • The task description

  • Current commitment

  • View and edit the percent complete either by adjusting the percent complete itself or by adjusting the number of points or hours that are complete

  • Assigned Users

You can display additional data (including custom data) on story cards. You might want to display additional fields on story cards for any number of reasons. For example, you might want to display the Customer ID if you are working on stories for multiple customers within the iteration, or you might want to display the Project Start Date or Project Completion Date. 

To configure story cards that are assigned to the agile team to display additional fields:

  1. Navigate to the 'People' area, then click the 'Teams' tab. 
  2. Select the agile team that you want to manage. 
  3. Click on the Team Settings link in the top right corner.​ 
  4. In the Agile  section, in the Additional Fields area, click Add Field, then select the field that you want to add to story cards. (These are the same fields that you can add when creating a filter or a report.)
    Repeat this process to add up to 3 additional fields to the story cards.
  5. Click Save Changes.

Configuring How Color Indicators Are Used for Stories on the Agile Story Board

By default, story board tiles in an agile iteration are color-coded according to the project that the story is associated with. (Each project is arbitrarily assigned a color on the story board.)

You can change this default behavior for each agile team. Colors for agile stories can be tied to story priority, owner, and so forth.

To change the behavior of how colors are assigned to stories for an agile team: 

  1. Navigate to the People area, then click the Teams tab. 
  2. Select the agile team that you want to manage.
  3. Click the Team Settings link in the upper-right corner.​ 

  4. In the Agile section, in the Associate Card Color to area, select from the following options:

    • Project: Colors are associated with the project that the story is tied to. (When a story is created, it must be associated with a project, as described in "Creating an Agile Story.") All tasks from the same project are displayed with the same color.

    • Free Form: All cards are displayed as blue by default until a user changes the color manually, as described in "Categorizing Stories by Color" in "Creating and Managing Agile Iterations." 

    • Priority: Colors are associated with the story priority, as follows:

      • High = Red

      • Medium = Yellow

      • Low = Green
        If your system administrator has configured custom priorities for your Workfront system, the highest priority is red, the second-highest is yellow, and the third-highest is green.

    • Task Owner: All stories with the same primary assignee are the same color.
      The primary assignee is the user who was first assigned to the task.

  5. Click Save Changes. 

Configuring the Issue List (Standard or Request)

You can configure the Issues tab to display issues in a standard list or a request list. The request list includes an option to allow users to volunteer to work on an issue.

  1. Navigate to the People area, then click the Teams tab. 
  2. Select the agile team that you want to manage. 
  3. Click the Team Settings link in the upper-right corner.​ 
  4. In the Agile section, in the On the Issues tab, show area, select from the following options:
    Standard issue list: Displays issues in a list and enables you to select a Filter, View, and Grouping to determine how the issues are displayed.
    issue_list_standard.png
    Team Request list (with "Work on it" button): Displays issues with a Work On It button. When a team member clicks Work On It, the issue is available in that user's Working On tab in the My Work area.
    Issues that have a resolving object are not displayed when viewing the issues in a Team Request list.
    issue_list_workonit.png
  5. Click Save Changes.

Considerations

Because users can be on more than one team, they can be on both agile and non-agile teams.