3 short videos to help you get started with Advanced Roadmaps
3 short videos to help you get started with Advanced Roadmaps
July 23, 2020 edited
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 started. Some of you have reached out, wanting to learn more about best practices, so I’ve created 3 quick videos to help you set up your plans for success.
If you have any follow-up questions to these videos, please leave a comment below. We’re here to make your planning experience with Advanced Roadmaps as smooth as possible, so if there are any other topics you’d like us to cover to help you get started, let us know in the comments.
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Thank you for the post @Roi Fine ! I think it's time to Subscribe to the Atlassian YouTube channel, so I will start receiving some updates. A small request, can you turn this into a playlist, so that it would be easy to find them under playlists section.
It would be great to generate priority in addition to tracking priority. Is there scorecard functionality, or something like that, available to enable auto or semi-auto rank-ordering, prioritisation?
The videos were taken on Jira Cloud, Premium edition. The Server/DC interface is a bit different but the same concepts and steps apply to both deployments.
Let me know if you got further feedback or questions.
Again, I want to go beyond just tracking priority. Is there a way to automatically generate priority (e.g. based on scorecard functionality, like productboard does, as I understand)
Our Premium free trial is ending, and we are making a tool decision by Friday.
This sounds like it might be a good use case for our Jira automation functionality. You could set up rules that trigger on issue update or issue create, check the values of certain fields, and then set the priority based on those conditions. Cross-project automation is also a Jira Software Cloud Premium feature and you can read more about it here: https://www.atlassian.com/software/jira/features/automation
Our Premium free trial for Advanced Maps is expiring July 31, and we are just launching a large, new, greenfield program. So we have more context to apply to our trial/PoC.
Could we please get a trial extension for two more weeks? Since our tool selection criteria has drastically changed, and we need more time to evaluate. Otherwise we have to make a rush decision in 2 days.
Thanks for the videos. Questions re: "Set up your teams for effective capacity planning":
1) if a team is assigned to multiple stories/epics across multiple projects, is there assumption that the bandwidth of the team is split uniformly? Or is there a way to specify bandwidth allocation per project vs time?
2) is team's capacity (pts/sprint) entered manually or can it be automatically determined from the past?
3) is there a way to do the capacity planning per individual, not team? (I guess workaround would be to create multiple teams of one, but seems quite an overhead).
4) is there a capacity report to see which teams are over/under allocated vs time?
1. Nope, there is no way to specify bandwidth allocation per project. In general, the capacity for a team is calculated per sprint/iteration of the team's Jira board (which can have issues from multiple projects).
2. The team's capacity is entered manually, but you can access the velocity report in Jira to get an insight into what the velocity is.
3. There is no dedicated feature for individual capacity, you can group/filter by the assignee field. This could give you visibility into issues assigned to each person.
4. There is no dedicated report per se. But you can share any view (including the capacity view) via a link (we're adding more sharing options soon).
Unfortunately, I can not figure out why this is not functioning. We have about 300 users on a standard Jira and I'm demoing to executive teams to convince them to move to premium. All I need is a little help and no one at Jira seems to be able to help. I get copied and pasted messages from your documentation which is incomplete at best. These videos also don't provide any level of detail.
This whole concept of internal/external teams and sprints is not clearly explained. And why would you even do that?
I've tried sourcing my issues from projects and I see only projected sprints. I tried sourcing my issues from boards and now I don't see sprints at all. also, each project was assigned a team, except none of the issues from the respective projects are associated with their teams. I've tried a dozen setups and have spent 2 weeks researching and reaching out Jira. The only thing I get is "customer advocate" that will email us every other asking us if we need any help, then never responds to our messages.
I'm sorry to hear about your experience so far. I'll be happy to chat and try to help. You can use this link to book some time with me - https://calendly.com/rfine/30min
Atlassian Team members are employees working across the company in a wide variety of roles.
August 13, 2020 edited
Apologies @ali.alavi, due to the time difference between your time zone and Australia's you created the meeting at 3am (whilst I was asleep) to start 5 hours later and didn't see the invite until I started work at 9am. I've adjusted the settings to avoid this happening in the future - My team is happy to reschedule though.
We are trialing Premium right now, and I am wondering if there is a way to get dates to roll-up to the Project level, or if this is something that might be coming out with a future release? Each of our Jira Projects are "true projects" with definitive start and end dates. It would be great if we could show that at this high level to our Corporate Staff, instead of having to show the dates at the Epic/Story level. My current band-aid is I created a Project in Jira with an Epic for each project in our company, and the start/end dates for each project, to show the full Corporate Roadmap. But, it would be great to not have to do that extra level of work and to be able to just pull in all existing projects into my Roadmap, and have the dates from the Epics/Stories roll-up to the Project level.
Great question! Unfortunately, that's not possible. We built Jira's projects with the purpose of being containers of work and not real projects with start and end dates. The issues in the Jira project are the "real" projects :-). If you are looking to roll up epic dates to a larger scope of work, I would recommend you to create an additional level of hierarchy above epic. Once you did that, you could link the epics to the higher up hierarchy and rollup the dates in your AR plan. Take a look at the second video in this post for instructions on how to configure an additional level of hierarchy above the epic. You can also check this doc.
We are implementing Advanced Roadmaps using Jira Data Center. The hierarchy is not working as expected, ie I can add/edit/see the parent link from the Epic screen, but cannot see the correlating Child issues on the Epics parent (we've named it Portfolio Epic). Advanced Roadmap configuration was set up exactly the way you highlighted in your video...
I can manually add the parent link from within the Jira Epic issue, but cannot drag and drop or bulk action update any Epics parents to Portfolio Epic from within the Advanced Roadmaps plan itself.
Regarding Hierarchy management. When we first started with Portfolio a couple years ago, we initially followed the recommendation to create a separate project for the higher level requirements. This is presented a good practice so we have an executive level of requirements for viewing.
However, over time the teams wanted the initiatives in their own projects. When we moved to that model we discovered this bug.
When creating new issues in Plans, the hierarchy works as intended and when sitting on an Epics, creating new stories, tasks, bugs are all that is offered. However when working on Epics in the Jira Project, and clicking on create issue, then the hierarchy is not enforced and users are actually defaulted to the top most level you created in your hierarchy.
Here's a picture of what I mean.,
There are two things that Atlassian should do I think:
1) Figure out how enforce the hierarchy offered through Advanced Roadmaps in the Project as well as in the Plan. (Creating stories within projects is a pretty frequent operation.
2) Update the documentation and spell out that creating a separate project for higher level requirements is not just for executives, but is also to separate the higher level requirements from the project in which the lower level requirements are being worked so as not to expose this known issue.
Roi, hoping you can answer a question for me. While in AR and in the left nav of issues, I click on the ellipse to create a new issue. It asks if I want to create a new epic or story. I choose story (We have several issue types at this story level), the question is: Is there a way to specify the issuetype that is defaulted?
Behavior seems to be similar to Jira, in that AFTER you select a type, that type will become the default, but only in that session and in THAT plan, if you go to another plan, it reverts back to the original default (Which unlike Jira, I cannot find a place to set that default). Wondering how that original default is determined and is there a way to set it, as my staff are looking for the default to be the "Story" issue type, but ours keeps defaulting to one of our custom issue types.
Appreciate any response, even if it is, "They have to live with it", I understand that they only need to pick the right issue type once and it will stay the same if they have multiple issues to create, but ... is there a way to set it, so I can get them to stop asking :-)
42 comments