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
Hi @Luis Cano ,
I'm on the Advanced Roadmaps team, as @Mikael Sandberg mentioned there are quite a few videos in the "Articles" space of this section of the community: https://community.atlassian.com/t5/Advanced-Roadmaps-articles/bg-p/portfolio-for-jira-articles
It would be really useful if you could give us a brief summary of what you're hoping to achieve with Advanced Roadmaps as that would help me give you more specific pointers of which resources to review. If you could provide an idea of the size of your org (number of teams, team size, number of projects, etc) and how you work (e.g. scrum, Kanban, SAFe, etc) and what problems you're trying to solve then that would be really helpful!
My organization uses JIRA (both scrum and Kanban) to plan and track the status of development work across functional teams. We've just recently learned about advanced roadmaps for JIRA and wondered it could be utilized to plan based on capacity, track dependencies, manage competing priorities, and explore alternative scenarios to plan and track multiple teams working on projects.
Thanks for that additional information @Luis Cano ... in which case I would suggest that Advanced Roadmaps is ideally suited to your needs as it ticks most of those boxes.
Essentially with Advanced Roadmaps you can create plans which source issues from one or more projects, boards or JQL filters (in any combination). It provides a Team field and team based capacity planning (we're looking at enhancing this to provide some individual capacity capabilities so if you have specific use cases around this then it would be great to hear them).
Each plan is a "sandbox" so the changes you make aren't immediately applied to issues until you commit them. You can also have multiple scenarios in a plan so you consider alternatives before settling on a specific plan.
It also provides a dedicated report for reviewing your dependencies that allows you to visualise the dependencies between teams. You can also view those dependencies in the roadmap and it will warn you when you have scheduling issues resulting from dependent issues being planned out of order.
As well as this you get additional hierarchy levels above Epic and an auto-scheduling algorithm to generate a roadmap from the estimates that you provide.
Most of these specific topics are covered in the demo video articles on this page: https://community.atlassian.com/t5/Advanced-Roadmaps-articles/bg-p/portfolio-for-jira-articles
I'd recommend you review that content and let me know if you have any specific questions!