This question seems to have been asked and answered a few times, but none of the answers really solves my teams' specific situation.
Some background info:
We have the following teams:
We have a custom JIRA project called "Charters" that contains a custom issue type called "Charter" (initiative) which is essentially a request to fund a project with a particular scope and outcome in mind. The charter issue is linked to a Business Case page in Confluence. Each charter advances through a workflow along a Kanban board, essentially from To Do to Approved.
Let's take an example of a charter called "Mosaic." This project will include some work for the Salesforce teams, the BI team, and possibly Web, too.
Once the Mosaic charter is Approved, the work is decomposed into epics and issues. My question is about where those epics and issues should reside.
Right now, we have the following JIRA projects, basically aligned with teams:
Since Mosaic spans multiple teams, it does not naturally fall into one of these buckets. Maybe it makes more sense to have a JIRA project called "Mosaic" instead of having team-centric JIRA projects.
Should JIRA projects be, well, projects? Or should they be team-centric? Or should they be product-centric (i.e., cross-team)?
One of the other major challenges we have is knowing that a particular bunch of epics and issues are actually part of Mosaic. If they are the only issues in the Mosaic JIRA project, then it's easy. But if Mosaic is spread across JIRA Projects, then how do we roll the up? And how to we prioritize the work of one team that may be working on issues in multiple JIRA projects?
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs