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
I am configuring a proof of concept for possible purchase of Portfolio. Our functional teams are set up as JIRA projects. We have initiatives that cross projects but there is always one functional team/jira project that 'owns' the initiative.
My question is...
Is it better to set up a project just for the initiatives and link each team/projects work to it or would it be better to set the initiative up under the 'owning' teams project and link other work from there?
What are the pro's and con's for each of those options
Thank you for any assistance you can provide
I think it depends on how your projects are used across the business - and how important access to Initiatives are.
As an example, I've run into several instances with this setup:
In these instances, we've used a separate project for Initiatives and Features to keep them contained. The project contains all Initiatives and Features across that slice of the business.
The benefits have been:
That is the best practice suggested by Atlassian; but you could have them in one project if (for example), Initiatives were product-based and so were your projects. Just depends on how you and your teams work!
The obvious pro for keep all levels in a single project is just that “ it’s all in one place/project”.
We have projects In our instance that have done it both ways. Some have even gone as far as having one project for initiatives, one project for Epics, and the multiple team level projects. One advantage that way is that you can give clients access to the initiative project and/or epic level so they can have some visibility/input at the top while keeping details around stories and tasks internal.