ace the change. CHAPTER 5 NETWORK ROADMAP EVOLUTION Roadmap Mutability mu-ta-ble Capable of change or of being changed in form, quality, or nature Merriam-Webster's Dictionary Mutability, in the context of roadmaps, is important in that it provides a way to assess whether the roadmaps are capable of changing over time. It also provides a way to check the effectiveness of the processes set in place for evolution of roadmaps under various conditions. Having introduced a reasonably acceptable definition for roadmap mutability, we propose the following as one of the ways to measure this. It is important to understand that while the concept of defining and measuring mutability of roadmaps seems important enough to us, we were unable to find specific references to this in our searches in standard publications. How can a change be defined as completed? One way is to define conditions of acceptance to confirm that the change is definitely in place in an entity where it is being changed. It follows that implementation of the change should be verifiable by inspection of the entity and also by observations associated with the behavior of the entity in cases where the change impacts some visible behavior of that change. If we were to define the conditions for successful change to a roadmap, they could include: All aspects of the roadmap are updated Viable plans for implementation of updated roadmap are available All stakeholders involved in roadmap communication have been updated about the changes All documentation related to the change is completed and available The resources necessary for achieving the changed roadmap are in place or arranged Based on such an acceptance of a change to a roadmap, mutability could be defined as a function of the number of valid changes initiated VS. the number of changes accepted successfully by the roadmap. A lower factor of accepted changes could imply that the organization still has a ways to go to achieve better roadmap mutability in order to evolve the network and the product at a rate 