s mentioned above, such as: Some roadmaps could be captured as simple textual statements describing the intent of the company to develop features in particular areas. Roadmaps could also be expressed in a graphical format with timelines expressed on an X axis and features and impacts being shown on a y axis. Figure 4-1, the roadmap depicting the Internet of Things, is an example of a graphical roadmap. TECHNOLOGY ROADMAP: THE INTERNET OF THINGS Software agents and advanced sensor fusion Technology Reach Miniaturization power- efficient electronics, and available spectrum Teleoperation and telepresence Ability to monitor and control distant objects Ability of devices located Physical-World indoors to receive geolocation signals Locating people and everyday objects Cost reduction leading Ubiquitous Positioning to diffusion into 2nd wave of applications Surveillance, security, healthcare, transport food safety, document Demand for expedited management logistics Vertical-Market Applications RFID tags for facilitating routing, inventorying and loss prevention Supply-Chain Helpers Source: SRI Consulting Business Intelligence Figure 4-1. Internet of Things roadmap Most commonly though, roadmaps tend to get developed and communicated through a set of slides or documents giving a detailed list of features like the different versions of the product, as well as showing the timelines and a graphical representation of the targets for the features through their impact. In spite of the differences in the ways roadmaps may get developed, represented, and communicated, most roadmaps should adhere to some standard maxims or implicit requirements about them. The most important requirement for any roadmap is that it should be able to address the different needs of different stakeholders to get sufficient information in sufficient detail. What we mean here is that for those stakeholders who are very interested to understand the features of a particular release of the product, the roadmap should indicate in very good detail the items 