Versions Compared

Version Old Version 17 New Version 18
Changes made by

Surendrasingh Sucharia

Surendrasingh Sucharia

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Market study

•Will give the ability to target the the right market

Outcome & Benefit

Action Items

Priority

Contributor (Who?)

AMJ '23

JAS '23

OND '23

JFM '24

1

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

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.

  1. MCQ / MMCQ, FTB, MTF (P2)

  2. Question reusability: Create within a QueSet, use in another (Visibility private (P3), Old ECML (P3)). Review question lifecycle.

  3. Attach audio

  4. Support 25k TPS scale

P1

Pooja, Kartheek

2

Value Proposition

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.

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

  • Market study

    • Will give the ability to target the the right market

    • Will be able Guide the product in the required direction

    • Understand potential inQuiry adoptions FTSO creating products/solutions.

P1

Suren, Pooja

3

Ease of use

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"

  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

P1

Gauraw, Kartheek

4

Experience and learn inQuiry. Help users imagine and visualise the possibilities using inQuiry

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

  2. Reference solution packages

P2

5

Testing Automation & 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

  1. Functional Testing Automation: Today the coverage is x/total APIs and x%. We want to achieve >90% coverage across all APIs.

  2. Performance Testing & Benchmarking: Today we don’t know this. We want to achieve <5% error rate. Expected scale: 25k TPS.

P1

Gauraw, Kartheek

6

Easy to ensure QuML compliance (Validate & Generate).

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

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

P1

7

Light-weight/low-code inQuiry package

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

P2

8•Will be able Guide the product in the required direction

Understand potential inQuiry adoptions FTSO creating products/solutions.

P2

9

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

•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

Out-of-the-box analytics for question usage, performance, and other question/question set related metrics.

P3

109

Activate Community engagement

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

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

P2

...