The Roadmap for Success

Roadmaps prioritised according to quantified business value to allow for transparency on project vision and direction.

ROADMAP FOR SUCCESS

Spring believes in iterative software development, including incremental rollout of major functionality.  We believe in starting with a MVP and iterating through phased releases.  Enter the Product Roadmap.

1. ROADMAP DEFINITION

A roadmap is the foundation for all strategic development efforts. A roadmap can be seen like a product backlog, with Themes in place of User Stories. A roadmap requires management and, like a backlog, should be periodically reassessed for validity.

2. ROADMAP PLANNING AND REASSESSMENT

It is critical that roadmaps undergo periodic reassessments to adjust for changes in priorities, any new external business situational changes, and for duration adjustments that are necessary to correct the course of projects. On a scaled project, roadmap reassessments should be formal activities and take place around every three months. Informal reassessment can take place outside of this time frame as information comes to light.

3. ROADMAP GROOMING AND PRIORITISATION

Roadmap Themes must be prioritised according to business value. Where possible, this business value should be quantified to allow for ease of communication and for (somewhat) objective prioritisation. Business stakeholders should be consulted for input on business value and on prioritisation.

Dependencies between Themes should also be considered, however should not necessarily be a deciding factor in prioritisation; if one Theme is dependent on another, consideration should be made to bringing forward the dependent component of the Theme only and not the entire Theme. The efficiency of doing this must however be considered on a case-by-case basis.

The roadmap must also be groomed.  The following activities take place during Grooming:

  • Removing Themes that are no longer relevant.
  • Creating new Themes in response to newly discovered needs.
  • Re-assessing the priority of Themes.
  • Performing an initial estimate of Themes, ideally based on MVP and subsequent work if details are known.
  • Splitting Themes into smaller projects as they become closer to development.

Spring can assist in your roadmap development.