Feature request process overview
Motivation
In 2024, we made a significant step forward by opening the Feature Request (FR) process to everyone.
We aim at engaging those who actually use Censhare to identify potentially the most impactful requests and to drive product development based on real user needs.
Customers and partners can now submit their ideas directly to the product management team instead of pushing their requests through the project or partner management and/or support tickets.
Technology
We are using FeatureOS, an open platform where everyone can:
submit an FR
search for existing FRs
get an overview of existing FRs and their implementation stage
vote on FRs created by others
comment on FRs and read other’s comments
This approach allows for public access to our FR process, enables a broader participation from customers and partners, and facilitates exchange between internal and external stakeholders on the early stages of feature development.
Please visit our feature request board. If you have Censhare credentials, please log in using them. If not, please contact your partner or project manager.
We strongly encourage you to submit your feature requests through this board!
Process overview
Below is the brief overview of our feature request process, from ideation to implementation. You will stay informed through the whole process and may be even involved on the earlier stages. Each stage is also reflected in the FR status on the board and each change triggers an email notification for the request creator and watchers of the request.
Submitting a new idea
Stakeholder submits an FR through the public feature request board. The product team is getting notified for every new submitted feature via email.
Evaluating the new FR
The product team holds a regular meeting to review the top FRs with the highest votes.
That’s why it is important that you upvote other feature requests!
Customers votes have higher priority for selecting an FR!
During the meeting, the team clarifies every feature request and estimates its potential business value.
If required, the stakeholder – you – will be contacted for additional details or clarification to support the evaluation of the FR.
If the feature has a clear business value, the product team assigns domain ownership and moves the FR to the next stage: the implementation pipeline. However, there is no guarantee of an immediate implementation and delivery of the feature.
If the team finds that the FR doesn’t provide enough value, it will have to be rejected. In this case, you will be provided an explanation.
Planning the implementation
A new feature is typically planned for the next major release in alignment with other priorities and the general product roadmap.
Planning involves internal clarification with the development team. The progress is also reflected on the board.
Delivering the feature
The actual development and delivery starts after the feature request process is finished. There is one status update for it on the feature request board, without much details, as this is out of scope.
Exact list of FR status values on the board and their meanings
States and statuses help you to understand the life cycle of a feature request.
Each state encompasses more than one status, to make the process more transparent and comprehensive, especially for external stakeholders.
State | Status | Description |
|---|---|---|
In Review | Submitted | A new feature has been proposed. |
In Review | The FR is under review by the product management team. | |
Pending Approval | The submitted request is awaiting a final approval before being moved into the implementation phase. | |
Planned | Backlog | The request has been accepted and moved to development backlog. This means that the feature has been approved and is scheduled for development. |
Refinement | The request requires further clarification before being moved forward to development. This is mainly done by the product team in collaboration with the development team, but stakeholders may be approached for additional information on this stage as well. | |
Pending implementation | Typically means that the request has been refined, approved, and is waiting for actual development to begin. | |
In Progress | In Implementation | The FR is actively being worked on by the development team. During this phase, it is being built, tested, and refined according to the specifications. |
Pending delivery | The feature has been fully developed and tested but has not yet been released to users. | |
Completed | The FR has been fully implemented and delivered with one of the releases. It can now be used. | |
Closed | The FR is closed without implementation and will no longer be considered for development. This can happen if the request has been rejected as having no business value or if it has been resolved in some other way, e.g., a duplicate request. | |
Please read the next article to learn the UI of our feature request board.