Programs portal for Controlled Crowdsourcing

Owned by Surendrasingh Sucharia
Last updated: Sept 17, 2019
5 min read

Instructions to use this template:

  1. Use this template to write the Product Requirements Document (PRD) for a single User JTBD or Initiative. 
  2. Each workflow within the PRD will correspond to an Epic in JIRA. Each User Story will correspond to a Story in JIRA that will be part of the Epic.
  3. Each section in the template has instructions, with examples explaining the type of content to be written in that section. 
  4. You may start typing into the section by eliminating the instructional text, or delete the instructional text after you have entered all content for the section.
  5. Repeat from section <Use Case 1> Overview for every use case in the User JTBD or Initiative

Introduction

To run a program an adopter needs a lot of content for capacity building of their personnel. Any ongoing program would have content already existing in paper or digital form. In order to enable the adopter to collate, curate, organise, and distribute content we will build a programs portal that will allow them to define scope of their program, contribution mode, content types, user roles and other details. 

Need to build following capabilities for Test Prep

  1. Ability to launch a new program
  2. Configure program URL with a human readable slug
  3. Configure scope of program by creating textbooks and tagging them to program ID (manual)
  4. Configure logic for linking content to textbook structure in this new program
  5. Configure question set template (blue print) for this program

Need to build following capabilities for Teacher & Student Enablement

  1. Ability to contribute different types of content by different set of users. For example, School 1-10 contribute Explanation and School 7-15 contribute Lesson Plan
  2. Support for uploading PDF and MP4 as various content types, such as Explanation, Experiential, Lesson Plan, Concept Map, etc
  3. Configure logic for these content types to be linked to textbook structure
  4. Configuring different menu items for each content type
  5. Configuring workflow for PDF & MP4. These will not have same workflow as questions

Types of Contribution Models : Controlled Crowdsourcing & Workshop

JTBD

  • Jobs To Be Done: 
    1. Contributor / Reviewer should be able to contribute all content types through on single portal
    2. Adopter / tenant would like to launch contribution portal aligned with a purpose driven programme to transform education in the State.
  • User Personas: This program would involve following user personas
    • Contributor : A school teacher, a well performing school teacher who has shown great performance in a subject / class.
    • Reviewer : A subject matter expert who is capable to reviewing content in a particular subject and judge its accuracy & relevance
    • Curator : Textbook owner will play the role of curator to finalise content that will be linked to the textbook
    • Textbook owner : Person responsible for ensuring content in a textbook is relevant, high quality, and available for all required chapters
    • Project owner : Person who will coordinate and ensure completion of project on time
  • System or Environment: All users are expected to use laptop or computers with minimum 2 GB RAM, Windows 7 or above, and on Chrome browser.

Requirement Specifications

This section consists of requirement specifications for specific use cases in the User JTBD. The requirements for each use case are elaborated in detail through sub-sections for:

  • Use case overview
  • Overall process workflow
  • Associated user stories 
  • Non-functional requirements
  • Localization requirements  
  • Telemetry requirements
  • Dependencies
  • Impact on other products
  • Impact on existing data  

Contribute all content types Overview

Contributor should be able to navigate upto 4 levels on Textbook units and contribute any of the content types at each level opened for contribution. Supported content types are Lesson Plan, Explanation Content, Experiential Content, and Concept Map

Contribute all content types Overall Process Workflow

Select Textbook > Select Chapter > Chapter level dashboard (View all units in this chapter with content types) > Contribute > Select content type > 

  • If Practice Set → allow user to create any question type and submit practice set for review, and edit when content is in draft / rejected state
  • If Lesson Plan / Explanation / Experiential → show upload page where user can upload, submit for review, and edit when content is in draft / rejected state 

Contribute all content types - Contributor workflow Overview

Contributor will be able to contribute all types of content using tools provided. Following are the details of each content type and the tools required for them.

Practice set

Contributor should be able to create a practice set using questions of different types. (Question types available to a user are configured by administrator when setting up the contribution portal)

At present all available question types should be available by default for a contributor to create Practice Set. (When setting up Contribution portal, admin should be able to configure specific content types such as MCQ Practice Set where only MCQ is available for that tool)

Questions are create in QuML format. For each question type, creation & consumption plugins are available along with QuML schema definition in the Assessment Model.

This is changing from the current model where contributor is creating questions > reviewers is reviewing questions > curator is selecting & publishing practice set which is linked to the textbook chapter. In the new model, contributor contributes practice set > reviewer reviews practice set > curator is selecting which practice set to link to textbook. As per the new model, the user might see multiple practice set per chapter.

Explanation / Lesson Plan / Experiential content

Contributor should be able to upload Lesson Plan / Explanation / Experiential in PDF or MP4 format. These file sizes are limited to 50 MB today. Contributor should be able to contribute more than one lesson plans by following the steps again. 

Contribute Practice Set / Lesson Plan / Explanation / Experiential 

Srl. No.User ActionExpected Result
1Login to contribution portal using Google IDUser is able to sign in using their signed in Google ID, user is provided with Contributor role, and is taken to Class, Subject selection screen
2Select Class, SubjectUser is able to select Class, Subject from the scope configured for contribution. On success, user is show a list of textbooks for selected Class, Subject
3Select Textbook

<Alternate Scenario 1>

Srl. No.User ActionExpected Result






Exception Scenarios

Srl. No.Error / ExceptionExpected Handling






Wireframes

https://whimsical.com/Mkw724DYoFyWrvNPxSUX7U 

For Future Release

JIRA Ticket ID

Textbook Setup for Contribution Overview

Textbook owner should be able to create textbooks with upto 4 level of units, tag topics to each unit wherever required, mark specific units for contribution, and open the textbook for contribution.

Textbook Setup for Contribution Overall Process Workflow

Users with Textbook creation rights


<Use Case 1 - User Story 1> Overview

<Main Scenario>

Srl. No.User ActionExpected Result






<Alternate Scenario 1>

Srl. No.User ActionExpected Result






Exception Scenarios

Srl. No.Error / ExceptionExpected Handling






Wireframes

https://whimsical.com/Mkw724DYoFyWrvNPxSUX7U 

For Future Release

JIRA Ticket ID

<Use Case 1 - User Story 2> Overview

Localization Requirements

UI ElementDescriptionLanguage(s)/ Locales Required



Telemetry Requirements

Event NameDescriptionPurpose

Non-Functional Requirements

Performance / Responsiveness RequirementsLoad/Volume RequirementsSecurity / Privacy Requirements



Impact on other Products/Solutions

Product/Solution ImpactedImpact Description


Impact on Existing Users/Data 

User/Data ImpactedImpact Description


Key Metrics

Srl. No.MetricPurpose of Metric