The Artima Developer Community Sponsored Link  Thinking Upside
Down Roadmaps vs Architectures by Andy Dent December 4, 2006
I'm currently engaged in a project, with colleagues at the
CSIRO, to develop a software roadmap.  The specific roadmap
we're producing involves much proprietary IP and so can't be
published at this time. However, I found a dearth of material on
how to produce such a roadmap and so have put together some
ideas, which I am allowed to publish.  The main
RoadmapDevelopment twiki page contains diagrams and people
signing up to be members of that twiki can comment on there.  At
the risk of subverting the page itself, I'll include a bit of
content here.  Roadmap as a Collection of Assets  (I am tempted
to use the word Artefacts instead of Assets but maybe Assets
best-represents things which may have existed before the roadmap
development activity started)  Instead of a relatively static
document, consider a roadmap as a collection of relatively small
assets which can be retrieved and presente