Understanding The Roadmap
The Verne product roadmap provides information on features currently being worked on and those under consideration for inclusion into the Verne product, either on a short or long-term basis. It also provides information on the planned order of implementation into Verne, and where possible, indicates the time-frame that the feature will be available.
There are, however, a number of considerations around the policies and processes affecting the roadmap that needs to be appreciated. Further, there are a number of caveats around the information provided as part of the roadmap that the reader should be familiar with.
Roadmap Content
The evaluation criteria for a feature differs according to the nature of the feature and where it might sit within the product, but typically covers criteria such as:
- Value from a functional perspective to clients;
- Ability to expand the services available within Verne, and hence increase the appeal of the product to other audiences;
- Technical/architectural fit within the Verne product;
- Scope for future enhancement of the feature.
The sources that provide input to the roadmap typically comprise:
- Feedback from the Verne Sales and Marketing team;
- Feedback from existing clients;
- Market research;
- Internal product suggestions.
Any updates to content will be made to the roadmap as and when they become apparent.
Content Prioritisation
The roadmap is the principal driver for feature enhancements. Other operational aspects are considered, such as stability and security enhancements.
The features and enhancements identified on the roadmap are evaluated and prioritised by the internal Verne steering group, with the driving factors being:
- The importance of the feature to clients;
- The urgency with which the feature is needed by clients;
- The logistics associated with the delivery of the feature – such as whether the delivery of a single feature might compromise the delivery date of a release;
- Any technical considerations or dependencies that arise with the delivery of a feature.
Any updates to prioritisation will be made to the roadmap as and when they become apparent.
Alignment to Releases/Version Builds
Where possible, the roadmap will identify the planned release that a feature will appear in. However it is important to realise that this is indicative only, and a release’s content is not formally advised by the roadmap. The purpose of planning and identifying a feature’s possible release is to provide as early an indication as possible as to when that feature might be available.
Further, a feature may not be part of a new release but maybe part of a minor version build of an existing release which is made available to clients, in keeping with Foster Moore’s Product Support and Maintenance Policy.
Any updates to features and their alignment to planned releases will be made to the roadmap as and when they become apparent.
Advised Dates
Within the roadmap, proposed delivery dates may be provided. However, these are indicative only and should be used as high-level guidance only. Once a release and its features are confirmed, notice of these will be advised.
Any updates to proposed dates will be made to the roadmap as and when they become apparent.
Changes to the Roadmap
Foster Moore reserves the right to make changes to the roadmap with respect to the information mentioned above. While every effort is made to ensure that the roadmap is an appropriate representation of the features that Foster Moore believes will continue to make Verne a compelling choice, there may be instances where the decision is taken to remove, delay, de-prioritise or add features within the roadmap.
In that respect, it must be noted that the roadmap is a guide only, and cannot be taken or relied upon as absolute fact of Verne’s future direction. Any decisions made by clients based on information provided within the roadmap remain the sole responsibility of that client.
