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

This report provides details of Diksha usage in terms of QR code Scans, Content Downloads, and Content Play, All the graphs show usage status per day. This report is updated every day.

JTBD

Jobs To Be Done: As a state admin, I want to have a look at various aspects of ETB such as consumption failures, etc.
User Personas: State, PMU
System or Environment:

Requirement Specifications

Date	Total QR Scans	Successful QR Scans	Failed Scans	Percentage (%) of Failed QR Scans	Total Content Downloads	Total Content Plays on App	Total Devices that played content on App	Content Play Time on App (in hours)	Total Content Plays on Portal	Content Play Time on Portal (in hours)	Total Content Plays	Total Content Play Time (in hours)

Description: This report provides details of Diksha usage in terms of QR code Scans, Content Downloads, and Content Play, All the graphs show usage status per day. This report is updated every day.

Date:

Total QR Scans: Total number of scans for the particular day

Logic: Total no. of scans done on QR codes which are linked to that state-specific books

Successful QR Scans: Total number of scans which rendered content successfully upon scan

Logic: QR code is present in ETB and has content linked

Failed Scans: Total number of scans for which the user did not get any linked content

Logic: QR Code is present in the ETB but no content linked

Percentage (%) of Failed QR Scans: Percentage of failed scans

Logic: Failed / Total

Total Content Downloads: Total number of content downloaded on a specific day

Logic: Total no of content downloaded either through QR code scans or Directly from the ETB

Total number of Content Plays on App: Total number of content played on the App

Logic: Total no of content played either through QR code scans or Directly from the ETB.

Total number of hours Content Play Time on App (in hours):

Logic: Total no of time spent on the content either through QR code scans or directly from ETB

Total number of Content Plays on Portal: Total number of content played on the portal

Logic: Total number of content which is linked to the ETB and played that day

Total number of hours Content Play Time on Portal (in hours):

Logic: Total time spent on the content which is linked to the ETB

Total number of Content Plays: Total no of content played both on App and the Portal

Logic: Total Content Plays on App + Total Content Plays on Portal

Total number of hours of Content Play Time including both app and portal (in hours):

Logic: Content Play Time on App (in hours) + Content Play Time on Portal (in hours)

<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

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

DIKSHA Usage Report