Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

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

JTBD

  • Jobs To Be Done: 
  • User Personas: State, PMU
  • System or Environment: 

Requirement Specifications

District Level Report


Weekly

Total no of scans by District: Total no of scans  from the District

Logic: Total no of devices which are linked to the specific district and did the scan on that specific day.

Total no of content Downloads in the district: Total no of contents downloaded  on a specific day in the district

Logic: Total no of devices which are linked to the specific district and downloaded the content which is linked to the ETB.    

Total no of Content play in District: Total no of content played in the district.

Logic: Total no of devices which are linked to the specific district and played the content which is linked to the ETB.

Total no of  Content play on Portal: Total no of content played on the portal in the district.

Logic: Total no of devices which are linked to the specific district and played the content on portal and those contents are linked to the ETB.

Total no of Content play on APP: Total no of content played on APP in the district.

Logic:  Total no of devices which are linked to the specific district and played the content on APP and those contents are linked to the ETB.

Content Play Time on Portal (in hours): Total no of time spent on content play on the portal.

Logic:  

Content Play Time on App (in hours):

Logic:

<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




  • No labels