We're a company that focuses on innovation, with a world class development team working across our portfolio of products. Our development team is based in our London office with the rest of our UK teams, which means we're getting first hand feedback direct to help us constantly improve our product mix.

We use an agile development methodology where we focus on 2 week sprints. At the end of the sprint the development is added into product either for general release or as part of a larger development for testing.

Developments break into a number of types which are treated in different ways:

Bugs - any critical bugs are dealt with immediately and any other type of bug is dealt with as a matter of priority

Cheese - this is the grey area where a development is working as scoped but customer feedback of "just doing x" would make it work much better (it's not a bug, it's not a feature... so we call it cheese). We try and achieve a few cheese items in every sprint, based on ongoing customer feedback.

New Features - typically features are implemented when we get multiple client requests, or if a single client requests something that we think will positively impact all our customers.

Paid For Features - if a client wants something to be prioritized or only they have requested it we will sometimes undertake paid-for developments. Note that because we are a cloud platform custom features will end up in all client platforms even if switched off. If a development could negatively affect other clients we will have to turn down the development.

Platform Automation and Efficiency - we have an ongoing stream of work to improve the deployment and upgrade of client platforms as well as constantly enhancing the underlying infrastructure.

Proof of Concept. - if we or a client have a great idea but we're not sure it will work or how it will work, sometimes we will undertake an initial proof of concept. We create a working prototype which can be released to a select number of pre-agreed beta clients for further feedback and refinement.

Outliers - these are our more ambitious ideas, typically pushing technology as far as it will go. These ideas don't always turn into working products but have led to some of the more exciting features and modules in the Vuture platform.

Security and Platform Stability -  we have a team  focused on the stability, future-proofing and security of the platform. This work is ongoing and typically doesn't form part of the sprints we are working on.

Our 2-weekly sprints are usually organised no more than 2 sprints in advance (so a 4 week roadmap at any one time) with the next sprint being organized from our backlog of many feature briefs and incoming requests (as of writing this there are several hundred development requests in the backlog). This allows us to tweak the ongoing update requirements based on market need. 

In order to focus on bigger picture developments, our backlog is organized into a structure we call "epics" - these are the global vision which currently shape our roadmap.

Because of the nature of our development process it's simply not realistic to give a roadmap feature list as the requirements are constantly evolving and a roadmap would be out of date almost as soon as it was published. 

How do developments get released to clients?

Vuture is a cloud based Software As A Service (SAAS) product, which means all clients get all updates usually on a weekly basis (unless there is some contractual reason not to do this). Unless the release is a patch, most developments are released as features, set to off. You then have the ability to turn on any new function for a particular role or container. Your Account Manager will keep you appraised of new releases as they come out so you can choose if you wish to release it to your users.

Approximately once a quarter, there will be a round up of all the releases in that quarter.  This round up usually takes the form of a webinar, delivered by the CTO - Tufan Unal.  There is also a dynamic Release Guide put into your platform for SuperAdmins to see when they log in.  It is dynamic because the Release Guide knows which features are appropriate to your firm's system and whether or not you already have them enabled.

Some developments are premium i.e. you need to pay to have them enabled. Typically these are new modules that your Account Manager can discuss and show you as they are released.