How AKIPS manages feature requests. Pinned Featured

We value your input and are excited to hear your ideas for improving the software. 

To ensure that we can effectively review and prioritise feature requests, we have established a new process that we'll be using from 1st July 2023 onwards and wanted to share with you how it works. 

Below, you will find an outline of how feature requests are reviewed, accepted, or rejected. 

1. Submission: 

• Users can submit feature requests via our community or a support ticket. Please provide a clear and concise description of the desired feature, along with any relevant details or use cases. Describe the business benefits. 
• It is helpful to include any supporting materials such as mock-ups, diagrams, or examples that illustrate the proposed feature.

2. Initial Review: 

• Our team will perform an initial review of all incoming feature requests. We will assess the feasibility, alignment with our product vision, and potential impact on user experience. 
• Requests that are incomplete, vague, or duplicate existing functionality may be flagged for clarification or may be rejected outright. 
• Feature requests that are well-documented and align with our product direction will proceed to the next stage. 

3. Evaluation and Prioritisation: 

• Accepted feature requests will undergo a thorough evaluation process. This involves analysing the technical complexity, development effort, and potential benefits. 
• Our team will assess the alignment of the feature request with our product roadmap and strategy. 
• Prioritisation will also consider factors such as user demand, potential impact on existing functionality, and resources available. 
• The outcome of this evaluation will determine the priority level assigned to the feature request. 

4. Communication: 

• We believe in transparency and keeping our users informed. You will receive a notification regarding the status of your feature request. 
• If additional information or clarification is needed, our team may reach out to you for further discussions. 
• For accepted feature requests, we may provide estimated timelines or indicate which future release is most likely to include the feature. 

5. Implementation: 

• Accepted feature requests will be assigned to the appropriate developerfor implementation. 
• The implementation timeline may vary based on the complexity of the feature, existing development commitments, and resource availability. 
• We strive to deliver high-quality features, and thorough testing and quality assurance will be performed during the development process. 

6. Release: 

• Once the feature has been implemented and thoroughly tested, it will be included in a future software release. 
• The release schedule may be influenced by factors such as feature dependencies, bug fixes, and overall product strategy. 
• We aim to provide regular updates to our users regarding upcoming releases and feature availability. 

Please note that while we value all user feedback, not all feature requests can be accepted or implemented immediately. Factors such as technical limitations, resource constraints, and conflicting priorities may result in the rejection or deferral of certain feature requests. 

Thank you for your valuable input and for being part of our software improvement journey.  

We appreciate your patience and understanding throughout this process. 

Kind regards,

Adam Leeflang

Head of Operations
AKIPS