{"id":47,"date":"2025-09-22T11:28:45","date_gmt":"2025-09-22T18:28:45","guid":{"rendered":"https:\/\/deepplanner.io\/documentation\/?post_type=lsvr_kba&p=47"},"modified":"2026-02-16T16:00:52","modified_gmt":"2026-02-17T00:00:52","slug":"creating-roadmap-forecast-step-by-step","status":"publish","type":"lsvr_kba","link":"https:\/\/deepplanner.io\/documentation\/knowledge-base\/creating-roadmap-forecast-step-by-step\/","title":{"rendered":"Creating a Roadmap Forecast: Step by Step Guide"},"content":{"rendered":"\n

Adaptive roadmap represents a forecast for delivery of features. <\/p>\n\n\n

\n
\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure><\/div>\n\n\n

Use the following steps to create a roadmap forecast:<\/h3>\n\n\n\n

Before start, create an account and space in Deep Planner<\/a>.<\/p>\n\n\n\n

1. Create or Import Epics<\/h3>\n\n\n\n

Epics define the features that need to be implemented.
To add a new epic, click \u201cCreate new\u201d in the Epics menu. 
For every epic, specify a name, description, and high-level estimate. It represents the technical work that must be completed to fulfill epic requirements.<\/p>\n\n\n

\n
\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure><\/div>\n\n\n


To import epics from JIRA, click \u201cImport\/Export\u201d in the Epics menu and follow the prompts.<\/p>\n\n\n

\n
\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure><\/div>\n\n\n

2. Define Epics Estimates and Dependencies<\/h3>\n\n\n\n

For required work list all items, their types and estimates in the “Technical Work” section of epics. <\/p>\n\n\n

\n
\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure><\/div>\n\n\n

To define dependencies, use the “Dependencies” section in the epic Description tab.<\/p>\n\n\n

\n
\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure><\/div>\n\n\n

3. Define Teams<\/h3>\n\n\n\n

Defining teams right is one of the most important actions in automated planning. To achieve this, go to the \u201cTeams\u201d page and click \u201cEdit.\u201d Click \u201cAdd a new Team.\u201d Specify name and click \u201cAdd a new Resource.\u201d Add resources that will correspond to team members, their responsibilities, and their daily capacities. Think of responsibilities as team roles. For recommendations on that topic, refer to the article \u201cHow to Define Teams.\u201d<\/a><\/p>\n\n\n

\n
\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure><\/div>\n\n\n

4. Add a Timebox<\/h3>\n\n\n\n

To add a timebox, navigate to the Roadmap page and click “Edit.” Click \u201cAdd Timebox.\u201d Enter start and end dates and the teams that will be available. Click \u201cSave.\u201d<\/p>\n\n\n

\n
\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure><\/div>\n\n\n
Drag and drop epics to the roadmap by the desired execution priority<\/strong><\/h5>\n\n\n\n

Drag and drop epics from the \u201cBacklog Epics\u201d column to the \u201cEpics\u201d table inside of the timebox.<\/p>\n\n\n

\n
\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure><\/div>\n\n\n

5. Preview the Changes<\/h3>\n\n\n\n

Click the \u201cPreview\u201d button. Oversee the generated schedule on a Gantt chart.<\/p>\n\n\n

\n
\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure><\/div>\n\n\n

6. Publish<\/h3>\n\n\n\n

Click “Save.” Confirm the recap before publishing.<\/p>\n\n\n

\n
\"\"<\/figure><\/div>\n\n\n

Click “Confirm and Save.” Adaptive roadmap is live and will now appear on the Dashboard and Roadmap pages.<\/p>\n\n\n\n

Note<\/strong>: To handle warnings, refer to the page \u201cSchedule Warnings\u201d<\/a> for guidance on solving the issues.<\/p>\n\n\n\n

Learn More<\/h3>\n\n\n\n

To learn more about the process such as fine tuning a roadmap, epic rescheduling and other nuances refer to the article Working with a Roadmap Builder<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"

Adaptive roadmap represents a forecast for delivery of features. Use the following steps to create a roadmap forecast: Before start, create an account and space in Deep Planner. 1. Create or Import Epics Epics define the features that need to be implemented.To add a new epic, click \u201cCreate new\u201d in the Epics menu. For every epic, […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","template":"","format":"standard","meta":{"footnotes":""},"lsvr_kba_cat":[6],"lsvr_kba_tag":[],"class_list":["post-47","lsvr_kba","type-lsvr_kba","status-publish","format-standard","hentry","lsvr_kba_cat-general"],"_links":{"self":[{"href":"https:\/\/deepplanner.io\/documentation\/wp-json\/wp\/v2\/lsvr_kba\/47","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/deepplanner.io\/documentation\/wp-json\/wp\/v2\/lsvr_kba"}],"about":[{"href":"https:\/\/deepplanner.io\/documentation\/wp-json\/wp\/v2\/types\/lsvr_kba"}],"author":[{"embeddable":true,"href":"https:\/\/deepplanner.io\/documentation\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/deepplanner.io\/documentation\/wp-json\/wp\/v2\/comments?post=47"}],"version-history":[{"count":25,"href":"https:\/\/deepplanner.io\/documentation\/wp-json\/wp\/v2\/lsvr_kba\/47\/revisions"}],"predecessor-version":[{"id":279,"href":"https:\/\/deepplanner.io\/documentation\/wp-json\/wp\/v2\/lsvr_kba\/47\/revisions\/279"}],"wp:attachment":[{"href":"https:\/\/deepplanner.io\/documentation\/wp-json\/wp\/v2\/media?parent=47"}],"wp:term":[{"taxonomy":"lsvr_kba_cat","embeddable":true,"href":"https:\/\/deepplanner.io\/documentation\/wp-json\/wp\/v2\/lsvr_kba_cat?post=47"},{"taxonomy":"lsvr_kba_tag","embeddable":true,"href":"https:\/\/deepplanner.io\/documentation\/wp-json\/wp\/v2\/lsvr_kba_tag?post=47"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}