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

Provide a brief description of the context and overview of the User JTBD or Initiative. 

JTBD

Use this section  to elaborate on:

  • Jobs To Be Done: As a State CM, I want to have a look at various aspects of ETB such as consumption failures, etc.
  • User Personas: The logged-in users who have State Admin role, Report Viewer role can access this report.
  • System or Environment: Works on for desktops with Chrome browser only.

Requirement Specifications

State CM Dashboards: All dashboards that need to be accessed by States will be configured under the dashboards page of that respective state. It can be accessed by users of respective states using Report Viewer role. In future versions, there will be a role-specific dashboard configuration.

In this report, we will be showing the 

  1. Learning Opportunities - Daily content use (Nationwide)
  2. Per Capita daily Content consumption by state
  3. Learning Operations - Daily Content Usage (Per State)

Following are the dashboards and their access mechanism

1. Learning Opportunities - Daily content use (Nationwide): This shows content plays. This graph will be configured in dashboards pages of MHRD and all States. The graph is updated daily. It will roll over for every 30 days.


<Main Scenario>

N/A

<Alternate Scenario 1>

N/A

Exception Scenarios

N/A

Wireframes


For Future Release

N/A

JIRA Ticket ID



Localization Requirements

N/A


Telemetry Requirements

N/A


Non-Functional Requirements

N/A


Impact on other Products/Solutions

N/A


Impact on Existing Users/Data 

N/A


Key Metrics

Specify the key metrics that should be tracked to measure the effectiveness of this use case in the following table. To add or remove rows, use the table functionality from the toolbar

Srl. No.MetricPurpose of Metric

Specify the metric to be tracked Explain why this metric should be tracked. e.g. tracking this metric will show the scale at which the functionality is used, or tracing this metric will help measure learning effectiveness, etc.