Instructions to use this template:

Use this template to write the Product Requirements Document (PRD) for a single User JTBD or Initiative.
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.
Each section in the template has instructions, with examples explaining the type of content to be written in that section.
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.
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

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

Need to build following capabilities for Teacher & Student Enablement

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
Support for uploading PDF and MP4 as various content types, such as Explanation, Experiential, Lesson Plan, Concept Map, etc
Configure logic for these content types to be linked to textbook structure
Configuring different menu items for each content type
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 Action	Expected Result

<Alternate Scenario 1>

Srl. No.	User Action	Expected Result

Exception Scenarios

Srl. No.	Error / Exception	Expected Handling

Wireframes

For Future Release

JIRA Ticket ID

<Use Case 1 - User Story 2> Overview

Localization Requirements

UI Element	Description	Language(s)/ Locales Required

Telemetry Requirements

Event Name	Description	Purpose

Non-Functional Requirements

Performance / Responsiveness Requirements	Load/Volume Requirements	Security / Privacy Requirements

Impact on other Products/Solutions

Product/Solution Impacted	Impact Description

Impact on Existing Users/Data

User/Data Impacted	Impact Description

Key Metrics

Srl. No.	Metric	Purpose of Metric

Programs portal for Controlled Crowdsourcing