1.7 Product Roadmap(B)

This is part 2 and continuation of the 1.6 Product Roadmap blog. At least, we understood that what do we mean about Product Roadmap.

The Product Roadmap is very important and it's contribution matters a lot for the success of our products at last. We understand that the Product Roadmap starts with the Product Vision and if our vision is not clear and has not fixed its problem then we end up building some different things.

I am sure you have heard that one wants to build X but end up with the Y. It is because of two reasons lack of vision which is actually the wrong things but during the experimentation you got something then it won't be a bad thing if it brings some value. The Product Team must be aware of the Product Vision and rectify the Vision for the Stakeholders.

In the previous blog, we have seen the tasks and must be completed in an individual quarter period of time. These tasks are the high-level features it must be separated from the Epics and User stories. Epics and User Stories are the features pertained to the Product Backlog. Product-Backlogs are the tasks and features which are to be completed. This might brings controversy that Product Roadmap brings the User Stories and Epics in the Product Roadmap or not. A few veterans say that the Product Roadmap must include only the high-level plans so that it could be measured and managed well.

But the other contrast, other veterans say that it must include the User Stories and Epics as well so that it would cover the granular level to high-level plan. But, this would make the Roadmap fill with information noise. One task contains N-number of User Stories which actually brings information noise and ambiguity while measuring the progress.

Which one is good/best, seriously doesn't know because it depends.

If we have very fewer features then we can include the User stories, Epic, and all high-level plans in the roadmap but still needs to be managed well with proper synchronization.