What? | Why? | Priority | Contributor (Who?) | AMJ '23 | JAS '23 | OND '23 | JFM '24 |
---|---|---|---|---|---|---|---|
Functional Testing Automation | Promise that it works with minimal time/effort spent every release by implementing test automation for all components. | P1 | |||||
Performance Testing | Ensures scale-ready with quantified benchmarks for microservice. | P2 | |||||
QuML Compliance | Ensures reusability, interoperability and longetivity of assets (question/sets) by complying with QuML specs (strict compliance). | P1 | |||||
Expand the available Question Types | Reduces the feature parity between ECML and QuML hence facilitating the switch from ECML to QuML Ability to compete in the market : By giving a wider variety of pre-built question types to the users, inQuiry is providing features at par with the competitors and hence driving adoptions. | P2 | |||||
Installation process is completely open-sourced | Gives the ability for anyone (including ED) to leverage inQuiry with minimal support | P2 | |||||
Local & Server Installation Script & its documentation | Adopter is be able to easily install inQuiry independently | P1 | |||||
Create a Tech FAQ and document steps to debug incase of commonly occuring issues | •Saves the team's time is debugging issues. | P3 | |||||
Market study | Understand potential inQuiry adoptions FTSO creating products/solutions. | P2 | |||||
Out-of-the-box analytics for question usage, performance, and other question/question set related metrics. | •This will generate necesssary information for questions and question set's analytics and hence make maximun use of the generated data and inQuiry's capabilities | P3 | |||||
Multilingual Support | •Enables the creators to create questions in different languages and also create multilingual questions ie same question in different languages | P2 | |||||
Identify items to be corrected and improve the inQuiry microsite | Will allow any potential Adoptor (or anybody else) to easily understand inQuiry. Inturn this should help in driving adoptions and also less effort to be spent by the team in explaining inquiry and what solutions can be implemented | P4 | |||||
WYSIWYG Creation | Allows users to easily edit and visualize the end user experince | P4 | |||||
Reusability of question by implementing visibility | Creators and organisations find it cost-effective to reuse questions. Currently questions created within a question set are not reusable across other question sets. Here are visibility functional needs. | ||||||
Community engagement | |||||||
Containerisation |
General
Content
Integrations
Add Comment