Versions Compared

Old Version 4

changes.mady.by.user Paluru Abhign Sai

Saved on

compared with

New Version 5

changes.mady.by.user Paluru Abhign Sai

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

JTBD

  • Jobs To Be Done: As a state admin, I want to have a look at the performance of each district in ETB such as consumption, failures, etc.
  • User Personas: State, PMU
  • System or Environment: 

District-wise

report for a number of

scans

should be added for the last 2 months 

Description:

This will provide only 2 months data, To identify which district is doing better this month than last month hence this report will get updated on a monthly basis. 

Details:

In this report, we will be displaying 2 months of data i.e; Last month and before last month. We will be showing how many scans are done in Diksha from each district and ranking should be allocated in the same order in graph 1.



In graph 2, based on the last month data, the ranking should be allocated to the district in the same order of graph 1.

      Reason: To compare which district is doing better in every month.

NOTE: This report should be updated on every month  1st with the latest last month data and before to last month data.

Latest last month data should be aligned in the ascending order of district ranks.




District Wise Unique Devices


        Description: This will provide only 2 months data, To identify which district is doing better this month than last month hence this report will get updated on a monthly basis.  

How many unique devices data got synced in The month before last month vs How many unique devices data got synced last month in that district

          Image Modified

Details:

In this report, we will be displaying 2 months of data i.e; Last month and before last month. We will be showing how many unique devices used Diksha from each district and ranking should be allocated in the same order in graph 1.

In graph 2, based on the last month data, the ranking should be allocated to the district in the same order of graph 1.


Reason: To compare which district is doing better in every month.

NOTE: This report should be updated on every month  1st with the latest last month data and before to last month data.

Latest last month data should be aligned in the ascending order of district ranks.

 


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