The roadmap is the set of functionalities and/or operational processes to be developed and implemented over a given period of time to achieve the business objectives.

Each product has a roadmap that takes into account the needs of the organization and shows the current status of the product, as well as any technical debt, enhancements, or new functionality it may have.

How is it built?

In IT, we consider the following aspects:

Definition of execution time. This depends on the status of each product and can be 1 month, 3 months, 1 year.
The goal determines what is to be accomplished during the roadmap execution period.
Periodicity of the reviews, also based on the product status, can be weekly, bi-weekly or monthly, they seek to review the status of planned functionalities and a preparation of the following ones.
This public document is on Google Drive, so the entire organization knows where IT is focusing its efforts across products.
A roadmap should not be confused with a backlog.
It is important to include the estimated time it will take to perform each function.

Responsibilities and functions

The product manager must always be responsible for the roadmap, from beginning to end.
All stack holders should be involved, suggesting new features, pointing out technical debt, and expressing their point of view on the opinions of others.

Audit and evaluation process

On a monthly basis, a roadmap progress report is prepared for each product, showing the status of commitments for the previous month and what is expected for the next month.

The dashboard shows the progress of each planned feature on a weekly basis.

Route plan by product

The route plan for each product is detailed below: