Enable course assessment through ED (for any training use-case).

1. Identify gaps in inQuiry for powering assessment use case (eg. visibility, diverse question types etc.,)

2. Power all the missing capabilities that are required for course assessment

Today it is one of the leading use-cases for ED adopters (DIKSHA & otherwise), but powered through ECML. Hence enabling this through QuML will help expose capabilities of inQuiry

P2

Value Proposition

Identify value propositions for independent software vendors (or IT teams)

Become more specific about who will find it more valuable, what will be their reason to believe in the benefits offered and thus having clarity on the right to play

P1

Ease of use

1. Simplify installation

2. Installation process is completely open-sourced

3. Local & Server Installation Script & its documentation

4. Make it cost-effective for any one to use

5. Enable health-monitoring

6. Create a Tech FAQ and document steps to debug incase of commonly occuring issues

Gives the ability for anyone (including ED) to leverage inQuiry with minimal support and know monitor the health this giving confidence to the adoptors
•Saves the team's time is debugging issues.
•Helps in Faster Resolution"

P1

Experience and learn inQuiry

1. Prototypes in experience centre, Microsite upgrade, completeness, and simplification

2. Reference solution packages

Help users imagine and visualise the possibilities using inQuiry

P2

Testing Automation & Benchmarking

1. Functional Testing Automation

2. Performance Testing & Benchmarking

Promise that it works with minimal time/effort spent every release by implementing test automation for all components

Ensures that microservice is Scale-ready; Get more confident about scale-readiness

P2

Easy to ensure QuML compliance (Validate & Generate).

We caught gaps in validation (by chance) and fixed them. Need to put a check so that it is always compliant.

Ensures that inQuiry follow the QuML spec and hence allow resability, interoperability and longetivity of its assets

P1

Light-weight/low-code inQuiry package

•Lower cloud infrastructure
•Simpler tech stack
•Easy to swap-out/swap-in dependencies (i.e. Knowlg).

P2

Market study

Understand potential inQuiry adoptions FTSO creating products/solutions.

•Will give the ability to target the the right market
•Will be able Guide the product in the required direction

P3

Out-of-the-box capabilities for visibility of learning outcomes.

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
•The users will be able to make informed decisions based the analytics data

P3

Activate Community engagement

•Co-created roadmap
•Regular community huddles
•Design thinking session
.................................

More contribution and support form the community, hence refining the product better

P3

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.
•Helps in Faster Resolution

P3

Market study

Understand potential inQuiry adoptions FTSO creating products/solutions.
•Will give the ability to target the the right market
•Will be able Guide the product in the required direction

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
•The users will be able to make informed decisions based the analytics data

P3

Multilingual Support

•Enables the creators to create questions in different languages and also create multilingual questions ie same question in different languages
•Also enables players to choose the language in which they would like to play
Hence making inQuiry accesible to a wide range of audience and also be able to power a variety of use cases

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.

Containerisation