Versions Compared

Key

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

...

Outcome

Action Items

Benefit

Priority

Contributor (Who?)

AMJ '23

JAS '23

OND '23

JFM '24

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.

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 to unlock imagination

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

V1 Roadmap

Last updated |

Status
colourRed
titleArchived

...