You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Some enterprises may have teams that provide value to other teams across many programs in a portfolio. You may want to represent these teams as centralized shared services teams in Jira Align.
Create a shared service team structure
To represent a shared service team as a centralized team, you should create a new program to encompass the shared services team. Then, create the shared services team as a Kanban team under the new program to represent the work the team does. This setup is the easiest to maintain, and the lightest weight to put into practice, especially if you’re using a connector to integrate Jira Align and Jira Software.
Note: When configuring the shared services team (and all Kanban teams) in Jira Align, be sure to set a normalized story size/LOE to help with consistent metrics in the Work in Process report and other reports that tie time and Kanban together.
Once you generate anchor sprints for the shared services and the other program teams, the other programs can then create dependencies on the shared services team. The shared services team and other programs can track the statuses of these dependencies on dependency maps, the Program Room, and the Program Board.
Track demand capacity with a shared services team
For shared services teams that interact on a more regular, planned basis with other teams, you can use a combination of Kanban and Agile teams to keep track of the team from an additional demand capacity perspective. Just add team members from the shared services team to the Agile teams that usually request the work, so that they’re on multiple teams. This reduces cross-program dependencies, allows for capacity reporting, and improves program predictability.
Once the shared services members have been added to the necessary Agile teams, allocations need to be set on those Agile teams to show how those users’ time is being consumed.