Skip to main content

Implementation of New Features Policy

note

This policy does not apply to bugs.

How we choose what to implement​

New features are implemented in Jadu software based on a variety of factors.

We combine feedback and suggestions from existing customers, requirements from newly awarded contracts and commercial opportunities, changes in legislation and best practice, accessibility, usability improvements and recommended security updates.

This information, combined with our medium and long-term product roadmaps, determine which features we implement and in which order.

We reserve the right to make changes to any previously published timescales, change the priority order of existing roadmap items, or choose not to deliver a feature in order to effectively meet the needs of our customer base.

How to track when features are implemented​

We publish a public changelog for each product release on HelloNext, there is also an RSS feed available should you wish to subscribe to updates. Release notes are posted to coincide with product releases at the point they become available to customers.

Cloud/SaaS Products​

  • Jadu Connect

We continuously improve and release new changes to our cloud platform, the product changelog will detail which features are included in a particular update.

Installed/Hybrid Products​

  • Jadu Central | Jadu Central Gateway
  • Jadu Content Portal
  • Jadu Digital Platform* | Jadu Digital Platform Lite*
  • Jadu Community Central* | Jadu Community Central Lite*
  • Jadu HUBis

When a new feature is ready for release it will be rolled into a version update which is then packaged and made available to customers who are running current versions of the software.

Customers will then be contacted by the Customer Success or Customer Support team to inform them when we intend to install this update onto their live system, communicate any expected downtime, and work together to agree on a suitable schedule of work. Customers can also request updates via Jadu Support.

For customers who have a User Acceptance Testing (UAT) environment we will roll out the update to this system in advance to allow organisations to thoroughly test the changes of a new release, identify any regressions in custom developments owned by themselves, and work with the Customer Success team to resolve any outstanding issues or to raise new tickets to address identified issues or bugs.

  • These products are packaged combinations of Jadu Connect and Jadu Central, the implementation details of a given feature will depend on which area of the software is affected.

Changelogs​

For a summary of changes, see the specific changelog for your product:

Product roadmaps​

We maintain a customer-facing (non-public) roadmap on HelloNext which covers features captured and tracked using the HelloNext boards, this typically will not contain all planned changes to the products, we communicate roadmaps at Jadu Academy days.

As an Agile organisation, we reserve the right to make changes to our roadmaps at any time to respond effectively to customer or business needs. We will endeavour to communicate these changes to any customers we know who have expressed interest or worked with us to define specific requirements through our regular catch up calls.

Feature suggestions​

Any user of the Jadu platform can request an account on HelloNext by submitting the shape our software form, in order to post new suggestions as well as upvoting or commenting on other suggestions.

We take the popularity of HelloNext posts as an indicator of customer demand, however the number of votes is only one of the signals we use to decide whether to commit to developing a feature.

Some features may require additional insight and experience from customers, in these instances typically we will invite a selection of organisations to take part in a meeting with members of the Jadu product team to discuss potential new features and to learn from their experience and gather any early requirements that may feed into the research and development phase of our development lifecycle. The insights from these conversations are captured.