My plan is rather complex.
As we defined them, initiatives are typically a capability / feature that is to be developed into our system, sometimes touching many areas thus involving a few development teams. I'd like to manage each initiative as a project with a project owner.
We therefore have ~30 initiatives on our yearly roadmap, each with 5-10 epics, allocated across ~8-10 teams based on the teams' functional product focus. Typically an initiative is allocated across a few teams, where an epic is allocated to a team. There will be dependencies within initiatives and also between epics and stories across initiatives.
We are looking at versions / releases as business milestones that we communicate to our business stakeholders. We therefore separated streams according to business channels / services. We have ~10 streams with 3-6 releases each. There could be a few initiatives contributing to a stream, but it is also possible that a certain initiative has epics that get released in different streams since they serve a few business channels.
In this complex environment it is hard to anticipate how JIRA Portfolio will prioritize and allocate the teams' efforts, nor it the teams will be properly utilized:
Did anyone recieve a response from Atlassian on any of this? These feature requests are essential for this plug in to work:
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