Roadmap for Jira is a plugin that can be installed on top of JIra. This presentation highlights key features and comments that this plugin provides that will help you take decision on buying it. This plugin is mainly used for Project Planning

1. Project Planning with
‘Roadmap for Jira’
Presented By: Parvez Ahmed

2. Agenda
1.Overview ‘Roadmap for Jira’
2.Steps of creating and tracking roadmap
3.Features of Jira
• Pros and Cons of each feature
4.Reports
5.Integration with Jira Agile

3. Overview
1.It’s a Plugin installed on top of Jira.
2.Costs 6000$
3.Product by RadiantMinds.

4. Steps
1. Create Roadmap
2. Add Epics and Stories
3. Assign Releases to each Epics and Stories
4. Assign Teams and members to each Epic and Story.
5. Assign Estimates.
6. Create Jira Issues
7. Calculate the Roadmap Timelines.
8. Track Project Progress with Time Spent

5. Create Roadmap
1. Roadmap can be created quickly
or imported from imatrix filter
2. Epics and Stories in tree
structure can be quickly created
in the roadmap.
3. Jira issues can be quickly created
for each story and Epic from
Roadmap
4. Stories can be prioritized by Drag
and Drop within Epic. Priority is
based on sequence of stories.
• Priority is not linked to Jira
priority or severity
Features Comments

6. Teams
1. Teams and members within the
team can be defined for a
Roadmap
2. Skills can be defined and
assigned to team members
3. Hours/week of availability of
each resource can be defined
4. Assign resource to each stories
• To be defined manually.
• Helps in defining separate
estimates for Java, .Net, DB,
Cognos etc.
• Hours/Week is the only
option. No days or weeks
• To be done manually
Features Comments

7. Releases
1. Releases can be defined for a
roadmap.
2. Epics and Stories can be assigned
to these Releases.
• Releases are NOT linked to
Fix version or Scheduledin
Release in Jira.
• User will have to manually
assign Jira issues to
respective releases
Features Comments

8. Estimates
1. Estimates can be defined in
Days/Hours.
2. Estimates for each skill can be
updated. E.g. .Net coding. Java
Coding, DB, PRD, Testing etc.
3. Security: There can be view
rights assigned to resources for
each roadmap.
• These estimates are not
linked to any Jira field.
• Security is at Roadmap level
and not team level.
Features Comments

9. Sprints
1. Calculate Sprints based on
estimates, resources and
Epic/story priority. • Any change in priority will be
recalculated.

10. Time Tracking
1. It shows time spent on each
story and indicates with Green
and Red color
• This is helpful if as we can
compare whether we are
overshooting the planned
estimates

11. Reports
1. No Dashboard reports available
2. Estimates cannot be exported to excel.
3. No Search Filter facility for Roadmap fields

12. Integration with Jira Agile
• No Integration between Jira Agile and Roadmap for Jira
• Roadmap Sprints are not linked to Jira Agile.
• Roadmap Sprints might become useless if we
manually change issues from Sprints in Agile Board.