llow this by discussing how roadmaps are implemented in most products. We conclude the setup with an understanding of the stakeholders involved in the road mapping process so that we can dig deeper into the framework later in the chapter. Roadmap Development Cycle We propose that at the highest level, a roadmap development can be modeled through the following four phases: Planning phase. Every cycle of the road mapping process starts with the planning phase, even if this is the first time the roadmap is being made. Execution phase. Once a roadmap has been planned, it needs to be executed as per the organization's execution models through programs and projects. Review phase. The roadmap under execution needs to be reviewed on a periodic basis and findings concluded. Update phase. Every roadmap review results in some updates to the roadmap, which may need to go through the planning cycle once again. Figure 6-1 illustrates the roadmap development cycle. Update Roadmap Execute Review Figure 6-1. Roadmap development cycle CHAPTER 6 A PROCESS FOR NETWORK ROADMAP EVOLUTION Also, throughout the roadmap development cycle, the roadmap and the changes to it should be communicated to all stakeholders, internal and external, as per the agreed-to communication guidelines set up for this. This is critical to the success of the roadmap in the following ways: It helps share a common vision across all stakeholders. It enables roadmap changes to get reviewed and gaps (if any) identified. It helps establish buy-in for the roadmap from the stakeholders. It enables stakeholders to understand and help improve the road mapping process where needed. Roadmap Execution: Programs, Projects, and Portfolios Ideally, all of the plans of an organization to be accomplished over a timeframe make up its portfolio. This portfolio may include development in many products in parallel. For each of these products, the organization needs to define what it wants to get developed as part of its roadmap. Each of the roadmaps may then get executed through o