Find the answers to these questions here:

Can’t find the answer to your question?

Ask us at: [email protected] or directly on WhatsApp

<aside> ❗ Small warning: You are now entering one of the greatest strengths (and subtleties) of RoadmapHero: planning. Take 10 minutes to read this content, and you'll become an expert in the field!

We invite you to read: Planning principles

</aside>

How to plan a ticket?

You have your backlog in front of you. To plan a ticket, from any grouping (except Initiative / Pain), simply swipe/slide a ticket in To plan to the left. You can then start planning.

If you’re not a fan of swiping (Tinder, take note), you can simply open the ticket, select the Plan section in the right column (on desktop) or a bit lower on the screen (on mobile), and click on Plan on Roadmap.

Next, you’ll be prompted to select the tasks to activate for each phase. Don’t worry, you’re not obligated to activate all tasks or phases. Choose what is relevant for the specific ticket. The tasks will be planned in the order they are configured, sequentially. Easy peasy!

Can I change the order of tasks?

Absolutely! You can set a default order of your tasks for each phase from Settings.

But if you want to customize the order for a specific ticket, you can do so by simply using drag and drop. This change will only apply to that ticket and will be considered in the planning.

How to plan tasks in discovery?

For the discovery phase, you’ll need to provide an estimate of the number of days and the time you want to dedicate per day for each expected task.

You can also use constraints and set a start or end date, or assign a specific builder to perform the action. These elements are optional but can be helpful for precise planning.

How to plan crafting, development, and deployment?

For the crafting, development, and deployment phases, you’ll need to indicate the complexity and estimate the time required for each task.

• Time estimation: This estimate is approximate and serves to standardize the use of the time gauge. Our algorithms will learn from the data provided by those who enter and perform the task.
• Use of constraints: As with discovery, you can use constraints to set dates and assign specific builders.

Think of it as a puzzle: you know how many pieces there are, and you have an approximate idea of how long it will take to complete.

What is the purpose of the “purple bar” display in the roadmap?

The “purple bar” allows you to choose when the ticket will appear as available in the roadmap. Once the ticket is planned, it will appear in the roadmap when the last task before the "purple bar" is theoretically completed.