Best Practices For Software Road Maps
App Dev Teams Reduce Uncertainties And Improve Delivery
October 31, 2011
Why Read This Report
In software development, road maps express to customers when valuable technology will be available. Unfortunately, software development includes many unpredictable elements, so the road map, which should reassure customers that they will receive what they need, often looks like something worth less than the project or product plan on which it's based. Fortunately, teams have developed three best practices for improving road maps: 1) attacking the sources of uncertainty; 2) choosing between different forms of road map; and 3) clarifying what commitments are possible in the short, medium, and long term.
Already a Client?
Log in to read this document.
Become a Forrester Client
Customers are the new market-makers, reshaping industries and changing how businesses compete and win. Success depends on how well and how fast you respond. Forrester Research gives you insights and frameworks aligned to your role to shorten the time between a great idea and a great outcome, helping your teams win in the age of the customer. Contact us to learn more.
This report is available for individual purchase ($499 USD).Purchase
Table of Contents
- Road Maps Define Relationships Between Producers And Consumers
- Reducing The Unpredictability Of Software Development
- Teams Redefine What "Road Map" Means
- Road Maps Include Three Time Horizons For Commitments
- Renegotiate The Road Map Contract
- Supplemental Material
- Related Research Documents
The Cybercriminal's Prize: Your Customer Data And Intellectual Property
September 2, 2015 | Heidi Shey
Create And Support The New Security Designer Role
April 27, 2015 | Tyler Shields
Quick Take: Use "Customer-Managed Keys" To Regain Control Of Your Data
February 10, 2015 | Tyler Shields