d simulation techniques to project and assess the impact of certain events on the project and roadmap execution. These results could then be used to understand the criticality and impact of project status on roadmap items and are used to take corrective and preventive actions on the roadmap and the projects under execution. Perform Roadmap Review: Output Roadmap Update Requests The main output of the perform roadmap review process is requests for actual updates of the roadmap. These roadmap update requests need to go through the roadmap change control process. At this stage, these are simply changes that are requested out of the roadmap due to the review process. They are not yet validated and quantified, and they need to be critically reviewed as part of the roadmap change control process before they can be planned as part of the roadmap. Perform Roadmap Change Control We define the perform roadmap change control process to validate the roadmap change requests and accept those that need to be accepted as valid changes and initiated further toward replanning of the roadmap. Figure 6-8 illustrates this process. CHAPTER 6 A PROCESS FOR NETWORK ROADMAP EVOLUTION Input Tools and Techniques Roadmap management Output Roadmap review board Roadmap update requests Management reviews Approved roadmap What -if analysis update requests Project status reports Organization input Expert judgment Project document updates Figure 6-8. Roadmap change control process Perform Roadmap Change Control: Input Roadmap Update Requests Roadmap update requests should have the following information: Reason for the update By which stakeholder or process the update was created Optional impacts or costs of making the update, including high-level estimates for project resources Impact of not making the update, in terms of cost to the organization, impact on customer, and SO forth Perform Roadmap Change Control: Tools and Techniques Roadmap Review Board We suggest formulation of a roadmap review board with key stakeholders as necessary for the roa