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:
- How releases belonging to different streams are prioritized vs. each other when competing on the same team resources?
- (feature request) I'd like to easily rank initiatives according to priorities rather than having to manage the individual 200 epics' priorities (or - define by prioritizing initiatives, then tweak some epics).
- Would be great to easily tweak the end result plan directly by eg. drag and drop along the timeline. Is there a simple way to mimic this behavior?
- Is there something I'm missing in this complexity? a way to make it more straight forward?
Thanks
Ran
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.