You can configure the following options for agile teams during or after the team is created. You create an agile team (Kanban or Scrum) in Adobe Workfront as described in Create an agile team.
You must have the following access to perform the steps in this article:
Adobe Workfront plan* | Any |
Adobe Workfront license* | Work or higher |
*To find out what plan or license type you have, contact your Workfront administrator.
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:
Click the Main Menu icon in the upper-right corner of Workfront, then click Teams.
Click the Switch team icon, then either select a new team from the drop-down menu or search for a team in the search bar.
Select the agile team that you want to manage.
Click the More menu, then select Edit.
Only team members with either a Plan or Work license see this option.
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.
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.
Click Save changes.
You can configure which columns are displayed on the agile story board for all iterations assigned to your team, or for a given project.
You can define the statuses that exist on the story board for the agile team. These are the only statuses that display on the story board.
To define the statuses that are available for the story board associated with the agile team:
Click the Main Menu icon in the upper-right corner of Workfront, then click Teams.
Click the Switch team icon , then either select a new team from the drop-down menu or search for a team in the search bar.
Select the agile team that you want to manage.
Click the More menu, then select Edit.
Only team members with either a Plan or Work license see this option.
In the Agile section, locate the Story Board area.
(Optional) Click Add Column to add an additional status column to the story board.
(Optional) Drag any status column using the drag-and-drop indicator to reorder the status columns on the story board. The first column can’t be moved, and you cannot drag another column in front of the first column.
Select both task and issue statuses. Task statuses are displayed as the column title for each column on the story board. The issue statuses you select map to the task statuses. This means that when you move an issue to another column of the story board, the issue status changes to the issue statuses shown here, and not to the name of the column on the story board (which reflects the task status).
Only locked system-wide statuses are available to select; you cannot select group-specific statuses. Also, the status of the first column always corresponds to New.
You can add custom statuses if your Workfront administrator has configured them; custom statuses can be configured as described in Create or edit a status.
When selecting issue statuses, the third column always defaults to Closed. If you have more than three columns, ensure that you manually update the columns to reflect the proper statuses.
Click Save changes.
For information about how to configure status columns for a project, see the section Create or customize an Agile view in the article Create or edit views in Adobe Workfront.
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 for tasks and issues:
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.
If you use a custom field on a story card, it cannot contain a period/dot in the name.
To configure story cards that are assigned to the agile team to display additional fields:
Click the Main Menu icon in the upper-right corner of Workfront, then click Teams.
Click the Switch team icon , then either select a new team from the drop-down menu or search for a team in the search bar.
Select the agile team that you want to manage.
Click the More menu, then select Edit.
Only team members with either a Plan or Work license see this option.
In the Agile section, type a field name to locate it.
Select the name of the field you’d like to add.
Type the Display name for the field to show on the story or issue card.
Click Save changes.
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:
Click the Main Menu icon in the upper-right corner of Workfront, then click Teams.
Click the Switch team icon , then either select a new team from the drop-down menu or search for a team in the search bar.
Select the agile team that you want to manage.
Click the More menu, then select Edit.
Only team members with either a Plan or Work license see this option.
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 Create 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 Categorize stories by color on the Scrum board.
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.
Click Save changes.
By default, when you add a work item to a Scrum iteration, the Planned Start Date and Planned Completion Date on the work item are modified to match the iteration start and end dates. You can choose to keep the original dates on all work items for the team.
Click the Main Menu icon in the upper-right corner of Adobe Workfront, then click Teams.
(Optional) Click the Switch team icon , then either select a new Scrum team from the drop-down menu or search for a team in the search bar.
Click the More menu, then select Edit.
Only team members with either a Plan or Work license see this option.
In the Agile section, in the When a Work Item is Added to an Iteration area, select from the following options:
Modify the Planned Start Date and Planned Completion Date to match the iteration start and end dates: When work items are added to an iteration, the work item dates are changed to the iteration dates.\
For more information on how the dates are modified, see the section Understand how adding stories affects task dates in the article Add stories to an existing iteration.
Do not modify the Planned Start Date and Planned Completion Date to match the iteration start and end dates: When work items are added to an iteration, the work items retain their original dates.
If you change the date option, dates for work items already on the iteration are not adjusted.
These options can affect dates when teams assign work items to each others’ iterations. For example, team A modifies work item dates to the iteration dates and team B does not modify work item dates. If team B assigns a work item to team A’s iteration, the work item dates will be changed. However, if team A assigns a work item to team B’s iteration, the dates will not change.
Click Save changes.