can be made here: In general, we consider the organization that is developing software and hardware components for the network to be the development organization. As for any organization that is operating on network development, there may be specific requirements for business continuity to be maintained. The network roadmap that is being developed may be constrained by such requirements as: Developing geographic redundancy among development teams Operating multiple teams to handle customer issues to satisfy service requirements Also, the organization that is buying the network for deployment, which would normally be a service provider, could also have specific business continuity plans under operation. These could determine the efficacy with which it can deploy, manage, and operate the network and the businesses that could run on it. These requirements should also be communicated to the PLM team responsible for customer interactions and should be included in the roadmap definition process as input. Approved Roadmap Update Requests Roadmap update requests that have been reviewed and approved by the roadmap change control process are input in the define roadmap process. These requests start a fresh cycle of roadmap planning for updating the roadmap that will have to be run through the roadmap development cycle. CHAPTER 6 A PROCESS FOR NETWORK ROADMAP EVOLUTION Resource Calendars Resource calendars provide critical input about the availability of existing resources and their competencies. It should also be clear from the resource calendars when certain resources and teams complete current engagements for ongoing projects and programs so the input is added to the roadmap under development. Define Roadmap: Tools and Techniques Workshops Facilitated and focused workshops are one of the best tools to define and arrive at the roadmap. Workshops can facilitate group decision making and also help in getting buy-in from necessary stakeholders for the roadmap. The following could be implemented in workshops to help arrive at