• Who is going to buy the product? Who is the target customer? Who is going to use the product? Who are its target users? • Which needs will the product address? What value does the product add? • Which product attributes are critical for meeting the needs selected and therefore for the success of the product? What will the product roughly look like and do? In which areas is the product going to excel? • How does the product compare against existing products, from both competitors and the same company? What are the product’s unique selling points? What is its target price? • How will the company make money from selling the product? What are the sources of revenue and what is the business model? • Is the product feasible? Can the company develop and sell the product? (Location 676)
effort. At first, the product backlog will contain visioning deliverables, such as “Prototypes exploring user interface design options are available” and “Customer interviews are carried out.” As the work progresses, the product backlog will include the high-level attributes that describe the future product, according to the product vision. (Location 866)
A product road map should state for each version the projected launch date, the target customers and their needs, and the top three to five features. (Location 946)
Be aware that a product road map can never replace carefully inspecting the market response and adapting the product accordingly. It simply states how we believe the product is likely to evolve based on our current understanding of the market. (Location 947)
Keep your eyes on the results, not the technologies” (Location 1535)
