Versions Compared

Old Version 1

changes.mady.by.user Surendrasingh Sucharia

Saved on

compared with

New Version 2

changes.mady.by.user Surendrasingh Sucharia

Saved on

Key

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

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

Table of Contents
outlinetrue

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: 
  • User Personas:
  • System or Environment: 

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  

<Use Case 1> Overview

<Use Case 1 Overall Process Workflow>


<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

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