dmap and the organization with the following focuses: Having necessary product and domain knowledge to assess the impact of the update request Having enough management or sponsor representation to approve the roadmap update requests Meetings of the board on a periodic basis to handle pending update requests Meetings of the board on an ad-hoc request or emergency basis, depending on the importance of the roadmap update request Assessment by the board as to the cost of updating the roadmap VS. the cost of not updating The rationale and decisions should be documented using standard agreed-upon procedures so the workings of the review board can be audited or revisited any time during roadmap execution. CHAPTER 6 A PROCESS FOR NETWORK ROADMAP EVOLUTION Perform Roadmap Change Control: Output Approved Roadmap Update Requests The prime difference with approved roadmap update requests would be the following information that could be added during the approval: Detailed impact analysis for the update requests Details regarding the approval given and rationale behind it Constraints that could qualify the approval in terms of: Special conditions considered Limitations to the schedule window within which the approved roadmap update request has to be processed Any other constraints Conditions under which the approval could be invalidated (if fany) Plan Resilience Management As mentioned in Chapter 5, the network roadmaps that are able to address resilience requirements are able to withstand challenges longer. Also, challenge response procedures are deployed faster in such networks. In plan resilience management, the focus is to decide the network resilience strategy and put in place a plan for implementing resilience management as part of the roadmap. This process is illustrated in Figure 6-9. Input Tools and Techniques Roadmap charter Output Roadmap Network resilience management plan models Resilience Enterprise/domain Strategies for management plan factors network resilience Organization input Workshops Expert judgment Figure