Our IT group is organized into 13 functional agile teams. As projects come into the queue, they are divided up into work that can be done by multiple teams based on the services or UIs that need to be updated. We would like to create one set of Epics for the project, then determine which teams have work to help complete each Epic. We are about to implement Portfolio for Jira, and would like to set up each of our functional teams as a shared team so that we can view the project work across those teams. This is working great in our testing at the story level, but we are only able to assign one Shared Team to an Epic, so it does not show up in any of the plans for the other teams.
I'm wondering if we are using Portfolio and the Shared Team concept in the way it was designed. Can you provide any insight?
Thanks!
Kelly - FirstBank
Hello Thomas!
I did not previously understand how the teams would roll up to the Epic level, but I actually just figured that out earlier today. Thank you!
Cheers
Kelly
Kelly, do you mind sharing your findings? I am also structured in this way.
Thanks!
Hi Matthew,
We assign the Shared Team at the Story level and then assign the parent Epic. If there are stories under the Epic with different teams assigned, the Epic will show in Portfolio for Jira as having multiple Shared Teams working on it.
I hope this helps!
Kelly