in the product's development to help it achieve further success and not get crippled as newer features are developed. Of course, overhauling the implementation technology need not be done in one all-or-nothing swoop if it is determined that it poses risks to the roadmap. The parts that make up the technology could be carefully analyzed to make a phased transition to more current technologies, in smaller increments, while making sure that the functionality that is already implemented is not broken. This needs some very careful planning and execution and would require help from the people with the best knowledge of the product and the domain to make the transition successful. The second aspect of technology, the technology that is provided to the customers through the product, can be addressed through some of the following aspects: Interfaces exposed by the product to the end users, like: Graphical user interfaces (GUIs) Protocol-based command line or other standardized interfaces, like representational state transfer (REST) APIs Standards implemented by the product: Standards as prescribed by 3GPP, ITU-T Other RFCs for specific parts like implementation of session initiation protocol (SIP) Operational procedures required to: Install Update Upgrade Troubleshoot the product All of these aspects should be evaluated against expectations; not only those that are explicitly stated in the requirements, but also those that are implicitly required by customers and other stakeholders to be part of the product. Inadequacies should be addressed by the product roadmap to make sure the product stays competitive. CHAPTER 4 NETWORK ROADMAPS Financial As connected as our world is today, finance plays a big role in impacting business decisions. Financial markets are all linked together globally to make every event of importance a global one. Investment climates tend to get very gloomy in such scenarios. This in turn would imply that global recessions are periods to be noted with great interest by business owners. During global melt