Learn how to set up Jira Software Cloud and integrate it with other products and applications.
Learn how to configure your Jira Software Cloud company-managed projects to suit your agile development processes.
Learn how to create, search, and work with issues in software projects, manage your profile, and more.
Learn how to get started, enable features, and manage and administer team-managed projects.
Create powerful rules to start automating your manual, repetitive processes.
Plan and view work across multiple teams, projects, and releases with Advanced Roadmaps.
A guide on how to deploy and monitor an application built on AWS using Atlassian and third-party tools.
Creating a plan in Advanced Roadmaps requires you to do two things: estimate and schedule issues.
Advanced Roadmaps is a sandbox environment meaning that any changes you make to your plan won’t be committed back to your Jira Software issues until you choose to do so.
Learn how to save your changes in the Review and save changes in Advanced Roadmaps section.
An estimate is an educated guess at how long you expect an issue will take to complete. You can base your estimations on either story points or time-based units (hours/days)--whichever aligns with how your teams work.
These estimates don’t need to be super accurate, but enough for planning purposes. It helps with scheduling issues and allows you to use features like capacity planning later on.
Once you have an idea of how big or small each task will be, the next step is to schedule them on your timeline. You can do this using dates which works exactly as you’d expect: you set a start and end date in the Date column, and Advanced Roadmaps places it on your timeline. Alternatively, you can place the schedule bar directly on your timeline.
Scrum teams can also schedule work according to sprints or releases. Advanced Roadmaps uses the dates of the sprint or release to create a corresponding schedule bar on your timeline. You can then save the sprint or release assignments to your issues in Jira to make planning for your team that much easier. Planning issues this way is less prescriptive, but it better aligns with the agile planning philosophy.
You can also define order in which your issues need to be done using what Advanced Roadmaps calls dependencies. With these, you can tell Advanced Roadmaps that an issue is reliant on another being completed first or that it needs to be completed before another one can begin.
When referencing dependencies, Advanced Roadmaps labels incoming dependencies with is blocked by, and outgoing dependencies with blocks.
For example, an issue titled “Get in the car” blocks an issue called “Drive to work” but is blocked by the issue “Get out of bed”. Dependencies aren’t necessary in any plan, but they help identify the order in which tasks must be done so you can schedule issues more effectively.
Was this helpful?