Background:
- 7 dev teams working in their own project.
- Issues types used today are Epics/Stories/Bugs/Tasks/Subtasks - managed by the teams within their project but some Epics include work from multiple projects.
- 3 week sprint cycle aligning their output with a common release to production ie v151, v152, v153 etc. We track this as the Fix Version in issues.
- Sprints include general features/bugs for all Brands we support and some Epics/Stories are tied to a specific or multiple Brands.
- Brand names are added to tickets using a multi-select custom field and are tracked across all issue types.
- Our company currently plans a Roadmap in a slide deck broken down by Quarter containing high level features that require effort from multiple teams.
- Some roadmap features need to be delivered by a certain date or for specific customers, others could potentially be deprioritized and new unplanned feature work added later.
- Dev teams point and plan work for the next sprint just days before the current sprint ends.
- Epics/Stories/Bugs/Tasks/Subtasks don't get assigned start/due dates, they just get "added" to a sprint using the Fix Version field once planned during the sprint prior.
We need to have a roadmap view in Jira that shows where we are within a specific Quarter to ensure we are going to deliver the features planned.
We need to present a view by Brand showing what Sprint specific features will be delivered in or were delivered.
We need a view of cross team dependencies/blockers.
We need to have a plan view where we can see potential impacts or trade-offs of rearranging/adding/removing work.
How can we start using Advanced Roadmaps? What process changes could we make?
Slide Deck Quarterly Work = Quarter Issue Type Q1, Q2, Q3, Q4?
Each Feature planned within a Quarter = Initiative?
Are Cross-Project releases needed? Are they helpful?
Can we view a roadmap status for the Quarters/Initiatives without the Epics/Stories from each project having defined Start/End dates?
Please share your thoughts!