ong with the projects through which it will be delivered. To make a roadmap concrete, an organization's agreed-upon horizon of features should be planned as part of the actual projects that have distinct content, timelines, resources, and a proper project plan. For example, it could be that roadmap items for the next 12 months are required to be planned in actual projects and releases and plans available for the same. Once project management plans are available, they should be executed as per plan. As project releases get executed and validated, the actual roadmap feature execution makes progress. Agile projects that feature validation could be tracked as a feature burn down to directly map to roadmap execution. Caution The closer project planning happens to roadmap definition, the better the success of the roadmap. Large time gaps between roadmap definition and project plans lead to stale information, miscommunication, incorrect prioritization, and ineffective products. Execute Roadmap: Output Validated Releases The prime output of the execute roadmap function tends to be product releases that are validated to be of acceptable quality per the project plan. Validated releases could also be verified by roadmap owners to meet the acceptance criteria for the features that were part of the plan. Project Deliverables Along with executable code, which is part of the validated release, the other project deliverables are also important, such as user guides, installation guides, online help manuals, and other configurations input. Roadmap Update Requests When project planning is undertaken, the roadmap's concrete information that could emerge for the actual project and planning constraints may require an update to the roadmap to reflect actual project planning. This may imply that some features do not fit in to the current release and may need to be postponed or swapped with some other features. This should be formulated as a roadmap update request and it needs to go through the process of an update roadmap SO this is ref