Hi, I'm exploring how to use advanced roadmaps in a 150-person organization including tech development, various non development tasks etc. So we have agile teams today and basically the closer to programming the more we use jira.
The idea now is to get more business activities not related to development into jira and to use advanced roadmaps to have an overview of say 4 years of planning (more details will be managed in the short time horizon but we do know some critical todos in the future and want them on the radar). The overall goal is to be more digitized in the daily work using confluence/jira (releasing some of the preassure on e-mails, metings etc.).
So generally I'm open to any advice on how to set this up! The idea is to work with epics down to sub-tasks. But then someone made a comment that the around 6 agile development teams are working with 12 week "initiatives". Obviously I cannot break down a 4 year planning into 12 week periods; but at the same time we do not want to interrupt how the existing teams use the system, rather align.
So will there be a challenge in having different time horizons for initiatives/epics etc. in the agile teams vs the long term planning?
And again ay general advice is appreciated; directly here or articles etc that can guide in the transformation to become more digitized.
So this was my first post, sorry for being a little general in the actual question statement :-)
Kind regards Oskar
Hi community, I’m Roi, a product manager working on Advanced Roadmaps for Jira. While Advanced Roadmaps is a powerful tool to plan and track work at scale, we know it can be challenging to get star...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events