Capturing Team Roster in a dynamic way

[Aline Chapman]

Hi community,

Today we use Confluence pages to capture team information and roster. We have one page per Value Stream with their respective teams information on that page.

The issue with using Confluence is that it's not possible to easily combine that into one data source so that management can see the teams information and roster for all Value Streams. We cannot use that information for reporting and metrics in or outside Jira.

We are considering configuring a Jira project to capture this information to make it more dynamic and provide the needed combined data source for visibility, metrics, reporting, etc.

I wanted to ask the community if anyone has any experience with team roster, does anyone use Jira for their team's information and roster? Do you do it in any other way? Is there any industry standards for this? Any recommendations or best practices you can share is much appreciated.

This is an example of the information per team we capture in Confluence (considering moving to Jira tickets):

Team Name

Theme

Engineering Manager

Product Manager

Scrum Master

Product Owner

Architects

Developers

Testers

Product Designer

Writer

Jira Board

[Robert Quinn]

We have started exploring Atlas, and it looks like the new custom fields might make it useful.

A sneak peek at Atlas custom fields - Atlassian Community

[Aline Chapman]

Thanks for the answer, @Robert Quinn . I looked into Atlas and the Teams functionality in Jira, but although that allows you to group your teams, it does not allow to assign the agile role each person plays in a team. Plus we use Jira Align so Atlas is not something we are interest in now. How do you handle teams roster today? Trying to get a sense of how others do this today. Thanks!