Create a Scrum Agile Team

If you have system administrator rights, you can create your Agile teams in the setup area but for anyone with a plan license, you can do it directly from the People area. For our example, we’ll do that. To create any team in Workfront, click on the Team dropdown menu and then click on Create New Team. The setup window pops up. So, let’s give the team a name; select the option to make it an Agile team; add the team members; and a team description.

Now to customize the new Agile team, click on the Team Settings option in the top right-hand corner and scroll down to the Agile section. From here, make sure that Scrum is selected. Below that, you can choose what status columns to use for both tasks and issues that are being used as stories on the storyboard. All work assignments must go through three essential stages that equate to the statuses of: new, in progress, and complete. Oftentimes, companies will use multiple in progress statuses to indicate the stage each work assignment must go through or they may have multiple complete statuses set up to kick off an approval process for a manager or customer review. Generally, you’ll want to choose similar status types for both tasks and issues in each individual column. Let’s keep the defaults for this example. The next setting you’ll need to decide on is points versus hours or what measurement we want to estimate the effort required to implement a user story. Points allow you to tell how hard or complex the story is, instead of planning out time required for each component of the story. For our creative marketing team, we’re going to select hours for estimating stories. On the Issues tab, we can choose if we want to display a standard issue list or the standard non-Agile team request list with the Work On It button. Most Agile teams choose the standard issue list, unless you have a workflow where team members can self-assign issues, instead of putting them on a storyboard. Depending on what type of work you typically include in an iteration, you may want to consider customizing the story card color to help visually organize your storyboard. For example, if the scrum team typically includes stories from multiple projects in their iterations, it may be beneficial to color-code our cards based on the project. If you need additional information on your story card, like description or priority, to make sure your team has all the information they need, you can add those work front fields here. When you’re all done, make sure to select Save Changes. That’s it! -