Consentua Roadmap11 May 2018
Now on Trello
We wanted to improve customer trust in our brand by publishing upcoming developments. Our brand ethos is always to be as open and transparent as possible.
We invite comments and votes for promoting changes on the existing cards. As well sugestons for new functions and enhancements that we can add to Consentua over time.
How it works
The cards have been allocated a target build. We give the builds obscure mammal names so we know which release we are working on.
So far we have outlined plans for the next two releases. These are Capybara and Dugong, which have a specific focus in each release. For Capybara the focus is all about the “Purposes’. For Dugong the focus is on the Consent Receipt. However, plans are always subject to change especially when driven by customer demands.
Vote with your thumbs
The intention is to have the majority of future functional change driven by customer demand. This seems much better than us sitting back at Consentua HQ thinking we know best. Yes, sometimes we will be selfish and promote a change that benefits Consentua, but only because that change will benefit the majority through improved performance, security, resilience and sometimes function.
To that end we ask our followers and users to help us prioritise the next functions and vote with your thumbs.
Understand the Key
We have colour coded the cards to give readers an understanding of where the change will impact and who it will benefit. What is interesting here is that we are shifting from an engineering driven set of changes to more customer driven changes. May that long continue!
The key breaks down into two different elements: 1) API, Dashboard & SDK - functional component impact area. 2) Customer Requested, Easier Management (for Consentua that is) and Client Centric function - identifies who the improving function will benefit.
To check out the Consentua Roadmap go to this link: