We were discussing roadmaps at Ryma the other day (yes we really talk about this stuff in our spare time for fun!) and the question was posed: Are people developing roadmaps to answer a question about release content or strategy. So, it is poll time again! Click here to participate in the poll.
If you are using a roadmap for strategy only you are missing one third of its use. It should assist in determining what is in your next release as well as provide a touch point to see how well your past release adhered to the course. If it went off course, why and do you need to intelligently adjust the roadmap?
Hi Larry, I like your point. A roadmap is for status checking of strategic direction (have I strayed from the goal), communicating short-term direction (what is in my next release) and long-term direction (my 3-year strategy). I like the retrospective perspective.
So far the survey results are interesting and I can see why the majority are selecting both. For most, I am sure "what is in my next release" is their strategy. I suspect if I had asked what question prompted you to build a roadmap, the first question would be leading the poll. - Stewart