1.6 Product Roadmap

First Clap for yourself because this blog gives you a simple and better understanding of the Product Roadmap.

We often plan things, how to start something, and then stick with the plan as we thought and accomplish the tasks. Let's understand this in this way, You want to go from the place "A" to Place "B". You would plan as:

1. What is the distance between A to B?

2. What kind and type of roads are available there?

3. What mode of communications(Bike, Car, Bus, Train) should be used?

4. Last is to follow the plan

This is nothing but the Roadmapping which you have planned and then accordingly you have followed. It would have different challenges and some changes are required while commuting but the basic concepts are the same.

#Product Roadmap:

When we are about to develop the product than the first plan for a strong roadmap. The roadmap must be real and address all the challenges. It should be "agile" because if it requires any changes then do that changes quickly and remove the barriers. It should have a timeline and the specific tasks which should be completed within the timeline.

The Product Roadmap starts with the Product Vision. Product Vision contains "Why What and How" to build the Products. This vision is decided by the Stakeholders and CEO, CPO, CTO. Later this VIsion converted into tasks and divided and given to different domain directors along with Product Managers who actually keep an eye for all domains for better product development.

The domain(Product, Sales, Marketing, etc) would decide the timeline(specific time period) to accomplish the tasks. After consensus within and outside the team, timelines would be decided. All teams would start working so that the tasks should be completed within the dedicated "timelines or Sprints". Sprints are basically an Agile process of the timelines. You would often hear in your company that it should be added in the next sprint by the agile team or development team.

Let's summarise the Roadmap as it has a timeline and their respective tasks and that should be completed within that time period. If we have a total of 12 tasks to be done in order to build the product and we have 1 year's of times then we could make 3 individual tasks for each quarter and in this way, we could complete all tasks. It actually gives you a structured way and coordinated information to think and plan to do things while developing the Product.