Agile team view vs Boards

[CBuckwal]

I’m looking for some guidance for setting up agile workflows for one of the new teams that we’re onboarding. I haven’t used agile before, but have gone through all I can find about agile and boards in Experience League, but I’m still not sure how to proceed. There seems to be a lot of changes in Workfront regarding agile functionality (Workstreams are unavailable to new users), so I’d like to build for the future functionality and not use a function that will be removed in the future. The team is requesting to work in sprints and be able to report on all their work. We require templates for all projects so I’d like that to continue for this new team.

We use requests, which are converted to either a project or task. My inclination is to have the team create projects with templates that include sprints and stories, then create a Board for the project. Any new tasks created on the board would be connected to the project. Does seem like a good way to do this? I looked into the agile teams set up with iteration, backlog and stories but I don’t see how I can connect to projects easily using the agile team view, buy I may be missing something. What is the value of setting up work in the Agile team view vs Boards?

Thanks for any input on this.

[monicacardoso · Accepted solution]

Hi @CBuckwal,

Thank you for your question! Your approach sounds well thought-out. Here are my thoughts:

Since your organization uses templates, you can create a template that includes sprints and stories, which will streamline setting up agile projects. For example: include sprints as parent tasks and structure stories as subtasks under each sprint.

You could also create a board linked to each project for an effective way to manage ongoing tasks. This setup will allow tasks created on the board to connect directly with the project’s structure, giving visibility into workload and progress.

Touching on requests, you can maintain your process of converting them into projects or tasks and have them flow naturally into the board setup. Also, having tasks and stories linked to projects from a template will make it easier to pull detailed reports or explore enhanced analytics.

The Agile team view is great for teams who only work in agile methodologies (sprints, iterations, backlogs) and don’t need to align closely with projects. The agile team structure is slightly detached from traditional project management, so it may lack flexibility in connecting with project templates and tasks.

Boards, on the other hand, are more flexible and allow you to visually organize and manage work within projects. They’re designed to give you the agile workflow without sacrificing connection to projects and templates.

Get started with boards

Agile

If additional assistance is needed to find recommendations or solutions to make this work specifically with your teams, you will want to reach out to your Account Executive, so they can assist you with getting some time scheduled with our Professional Services team.

- Monica

[CBuckwal]

Thanks for this explanation, Monica. This is really helpful.