ng activity. We expect the following participants to be part of these roadmap development workshops: representatives from critical stakeholder groups for the product, including project sponsor, senior management, product development team, product support team, systems engineering, product validation/testing team, quality assurance team, and subject matter experts. Workshops should focus on getting consistent and valid input about how the product roadmap will be defined, documented, communicated, managed, executed, reviewed, and updated. Expert Judgment Although a workshop is a good way to collect input and brainstorm issues and solutions, the final decisions on the roadmap plan should be determined by expert judgment, as executed by business development personnel and approved by senior management team. Develop Roadmap Management Plan: Output The roadmap management plan could be a high-level document listing guidelines and referencing other plans for operations, or it could be a detailed document giving exact procedures and fine points related to how roadmaps will be developed and managed. The following critical items should be part of every roadmap management plan: Decisions about how the roadmap will be documented, including the following template elements: Description of product or domain Standards of compliance, if any, for the roadmap Format of the roadmap, as in: Textual representation Block diagrams Timeline charts VS. feature Multiple levels of roadmap information Configuration management of the roadmap, such as how it will be versioned and where it will be stored Caveats, if any, about features listed in the roadmap and what level of confidence can be associated with them CHAPTER 6 A PROCESS FOR NETWORK ROADMAP EVOLUTION Guidelines about roadmap communication to stakeholders and critically to customers with information about: When communication will be made Who is responsible for the communication What information will be communicated How will customer feedback be collected Guidelines about how the roadma