![\"\"](\"https:\/\/deepplanner.io\/documentation\/wp-content\/uploads\/2025\/11\/roadmap_progress-1-1024x304.jpg\")
<\/figure><\/div>\n\n\nAdding a Timebox<\/h3>\n\n\n\n
A timebox defines the calendar boundaries for planning. A timebox can be a month, a quarter, or just a particular milestone period. Multiple timeboxes can be added to a single roadmap, but their dates must not overlap.<\/p>\n\n\n\n
To add a timebox, click the \u201cAdd a Timebox\u201d button inside the editor. Specify the following information:<\/p>\n\n\n\n
- \n
- Name: <\/strong>Specify the timebox name, such as \u201cQ1 2026\u201d or \u201cMVP 1\u201d<\/li>\n\n\n\n
- Start Date:<\/strong> The start date of the target planning period<\/li>\n\n\n\n
- End Date:<\/strong> The end date of the target planning period<\/li>\n\n\n\n
- Custom Dates: Optional.<\/strong> Select or unselect particular dates inside the period, such as weekends or holidays<\/li>\n\n\n\n
- Teams:<\/strong> Specify the particular teams that will be working in that timebox<\/li>\n<\/ol>\n\n\n\n
The new timebox will appear in the list of timeboxes for that roadmap and include its name, start date, and end date. You can always navigate between timeboxes by selecting a different one from the list.<\/p>\n\n\n\n
Scheduling an Epic<\/h3>\n\n\n\n
To schedule an epic drag it from the \u201cBacklog\u201d table and drop to the timebox \u201cEpics\u201d table inside the editor. This will trigger automated scheduling. Epic will be added to the end of the list and scheduled last. To change the priority of the epic and schedule it prior to the other epics, drag the epic to the top of the list or at the desired position. The scheduler will schedule in the order specified.<\/p>\n\n\n\n
When scheduling an epic, the system takes as a main factor the epic high-level estimate, or the remaining estimate if work was marked as partially completed. The system finds the team assigned to a timebox that matches the epic by its capacity and responsibilities available under team resources. If certain team resources are already occupied or unavailable, then the system may attempt to schedule it to another team or share it between multiple teams.<\/p>\n\n\n\n
The system uses Today\u2019s Date as a baseline and then calculates the amount of calendar days for epic completion based on the number of days required for the team to implement that epic. If the team is scarce of a particular resource, more calendar days will be assigned in order to implement the epic<\/p>\n\n\n\n
Example<\/strong>. <\/p>\n\n\n\n
Epic Secure Notepad has a high-level estimate record, including development (10 man-days) and testing (10 man-days). Team Lion has a resource \u201cDevelopers\u201d available in 2 man-days daily capacity. Team Eagle has a resource \u201cTesting\u201d available in 1 man-days capacity. <\/p>\n\n\n\n
Given that Team Lion needs 5 calendar days to complete their part and Team Eagle needs 10 calendar days to complete their part, the system will assign 10 calendar days to both teams in order to implement the epic Secure Notepad. The system assigns the longest time span. Team Lion however will still hold 50% of their capacity that could be allocated to other epics.<\/p>\n\n\n\n
Unscheduling an Epic<\/h3>\n\n\n\n
To unschedule an epic, click on the \u201cTrash\u201d button in its row in the Epics table. This will trigger an automatic unscheduling of the epic and regeneration of schedules.<\/p>\n\n\n\n
Rescheduling Delayed Epics or Epics in Progress<\/h3>\n\n\n\n
The system doesn\u2019t reschedule any epics automatically that are delayed or were started and are still in progress. Schedules will remain consistent, even if they are re-estimated or moved higher in the priority order. However, it is possible to force rescheduling of these epics manually. <\/p>\n\n\n\n
In order to do so, click on the epic and navigate to the right sidebar. Open the \u201cCalendar\u201d tab and find the \u201cReplan\u201d button. Clicking \u201cReplan\u201d will trigger re-including the epic to the schedule from today\u2019s baseline based on the remaining estimate, priority, and dependencies of the epic. <\/p>\n\n\n\n
It is also possible to reschedule all delayed epics in a timebox. In order to do that, click on \u201cActions\u201d by the timebox and click \u201cReplan All Delayed Epics\u201d in the dropdown menu.<\/p>\n\n\n\n
Updating Epics and Teams with new Data<\/h3>\n\n\n\n
Data, such as high-level estimates and team capacities, need to be changed outside of the roadmap editor in Space. In that case, the roadmap editor will be updated automatically with new estimates, team capacities, and backlog data every time the user reopens or returns to it from a different browser screen. The system automatically applies the updates and rebuilds schedules to accommodate the changes. It will show a notification if any updates are applied to the schedule. <\/p>\n\n\n\n
In some browsers, updates may not trigger automatically after returning from other screens. In that case, they can be triggered manually by clicking on the \u201cRefresh\u201d button inside the editor. <\/p>\n\n\n\n
Fine-tuning the Epic Plan<\/h3>\n\n\n\n
Defining Preferred Teams<\/h4>\n\n\n\n
It is possible to assign desired teams to a particular epic. In order to do that, click on the epic and navigate to the right sidebar. Open the \u201cSchedule\u201d tab. Click \u201cAdd a Preferred Team.\u201d The teams added in this setting will be prioritized in the schedule. However, if they are not available or lack resources, the epic can be scheduled to other teams.<\/p>\n\n\n\n
Defining the Earliest Start Date<\/h4>\n\n\n\n
If an epic has an external dependency, its plan can be adjusted by specifying the earliest start date. The system will not schedule the epic to dates prior to that date. In order to do that, click on the epic and navigate to the right sidebar. Open the \u201cSchedule\u201d tab. Select the date from the dropdown, \u201cStart no earlier than.\u201d<\/p>\n\n\n\n
Excluding Nice to Have User Stories<\/h4>\n\n\n\n
Sometimes it\u2019s useful to experiment with epic scope while working on a schedule. Deep Planner enables that through the ability to exclude user stories that are marked as \u201cNice to Have\u201d in the epic details. In order to do that, click on the epic and navigate to the right sidebar. Open the \u201cInformation\u201d tab. Select \u201cExclude Nice To Have User Stories\u201d checkbox. Upon selection, the system will update the estimate and will exclude any work items that explicitly relate to the user stories that are marked as \u201cNice to Have\u201d in the epic details.<\/p>\n\n\n\n
Manual Schedule Mode<\/h4>\n\n\n\n
Although Deep Planner is an automated scheduler, it is possible in exceptional situations to manually assign start dates, end dates, and teams to an epic. In order to do that, click on the epic and navigate to the right sidebar. Open the \u201cSchedule\u201d tab. Shift the \u201cSchedule Mode\u201d toggle to \u201cManual.\u201d Then specify the start date, end date, and teams. Team resources will be assigned at full capacity for the selected time range.<\/p>\n\n\n\n
Previewing changes<\/h3>\n\n\n\n
To preview the changes, click on the \u201cPreview\u201d button in the left sidebar. The system will display the schedule in the Dashboard view. To learn more about Dashboard, navigate to the \u201cUsing the Dashboard\u201d documentation page.<\/p>\n","protected":false},"excerpt":{"rendered":"
The roadmap builder is a tool that allows you to create a roadmap forecast by adding epics to a schedule. In Deep Planner, the schedule dates for epics are not assigned directly but evaluated and predicted by the system based on several factors, such as a high-level estimate, teams’ capacity, and the desired sequence of […]<\/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-213","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\/213","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=213"}],"version-history":[{"count":7,"href":"https:\/\/deepplanner.io\/documentation\/wp-json\/wp\/v2\/lsvr_kba\/213\/revisions"}],"predecessor-version":[{"id":306,"href":"https:\/\/deepplanner.io\/documentation\/wp-json\/wp\/v2\/lsvr_kba\/213\/revisions\/306"}],"wp:attachment":[{"href":"https:\/\/deepplanner.io\/documentation\/wp-json\/wp\/v2\/media?parent=213"}],"wp:term":[{"taxonomy":"lsvr_kba_cat","embeddable":true,"href":"https:\/\/deepplanner.io\/documentation\/wp-json\/wp\/v2\/lsvr_kba_cat?post=213"},{"taxonomy":"lsvr_kba_tag","embeddable":true,"href":"https:\/\/deepplanner.io\/documentation\/wp-json\/wp\/v2\/lsvr_kba_tag?post=213"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
- Start Date:<\/strong> The start date of the target planning period<\/li>\n\n\n\n