Last Updated: 21 December, 2022
What is it?
A roadmap is the route you plan for your project to take. What has to get done first, what relies on other parts, what’s more important, what’s less important?
A general rule of thumb is that design needs to be done before engineering, so keeping track of which parts of your project are going to be completed in what order can help you make sure nobody remains idle for too long. While you’re waiting for design to get started with frontend, you still know what features need to be built, so it’s time to figure out what data is required. And while you’re waiting for the engineers to finish up, it’s time to work on designing the next feature, or time to work on some marketing for Demo Day.
How do I apply roadmapping?
There are many tools you can use. You just need something that lets you visualize dependencies between tickets. Write a list of all the tickets you need completed and the time frames they will consume. Then, note which tickets rely on other tickets, and place those in the corresponding order. Your roadmap should start to fall into place.
The challenge is not placing everything like a puzzle, but making sure time estimates are relatively accurate and team members communicate and remain on the same page.
While it’s not the most common tool, Notion has some pretty robust and accessible roadmapping tools in its
- Note how the yellow arrow indicates
Implement Registration Flowrelies on
Design Registration Flow. Whereas,
Setup Backendis independent and does not block another Ticket (yet).