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

JTBD

Jobs To Be Done: As a product manager/program manager, I want to be able to make critical decisions about outreach campaigns, content usability, and product usability.
User Personas: product manager/program manager and developers
System or Environment:

Requirement Specifications

Acceptance Criteria

All key user actions and system responses for the FTU, repeat users and engagement analysis also should be instrumented and documented. This encompasses all key actions in the onboarding steps, scan to play, textbook navigation to play along with cohort information like user type, B/M/G, language selection and location.
The new instrumented values should be added along with the existing instrumented values.
The new instrumented values are defined by the pagewise. There are some user actions that are repeated in the multiple pages (eg: pop-ups and back buttons), for those user actions instrumentation format should be the same in all the pages.
All definitions used in the reports are to be validated by QA for every release.

Telemetry Requirements

Page Name	Event Type	Event Name	eid	env	actor type	edata type	edata subtype	edata_id (INTERACT)	pageid	contextrollup.l1	cdata[0].type	cdata[0].value	props (AUDIT)	duration (IMPRESSION)
Splash page	System Response	Display the splash page	IMPRESSION	onboarding		page-loaded			splash		First time user			<time to show loaded page>
Language selection	System Response	Display Initial Onboarding Preferred Language page	IMPRESSION	onboarding		page-loaded			language					<time to show loaded page>
	User Action	Click a language	INTERACT	onboarding	User	select-language		<new language code>	language
	User Action	Click to change Language	INTERACT	onboarding	User	select-language	<previous language code>	<new language code>	language
	User Action	Click "Continue" after selecting the language	INTERACT	onboarding	User	select-continue	success	<language code> (e.g. en, te)	language
	User Action	Click "Continue" without selecting the language	INTERACT	onboarding	User	select-continue	fail		language
	System Response	Language is set for the device	AUDIT	onboarding		set-language		<language code>	language				language
User type selection	System Response	Display user type selection page	IMPRESSION	onboarding		page-loaded			usertype					<time to show loaded page>
	User Action	Click user type	INTERACT	onboarding	User	select-usertype			usertype		UserType	<usertype> (Student/Teacher)
	User Action	Click "Continue As" User type	INTERACT	onboarding	User	select-continue			usertype		UserType	<usertype> (Student/Teacher)
	System Response	User type set for the device	AUDIT	onboarding		set-usertype			usertype
	User Action	Click"Back" from the UI	INTERACT	onboarding	User	select-back	ui		usertype
	User Action	Click"Back" from device	INTERACT	onboarding	User	select-back	device		usertype
Scan or manual selection	System Response	Request for QR / B,M,C Page	IMPRESSION	onboarding		page-request			scan-or-manual
	System Response	QR / Board page loaded (Total boards count)	IMPRESSION	onboarding		page-loaded			scan-or-manual		CountBoard	<Total boards count>
	User Action	Click on scan QR code	INTERACT	onboarding	User	select-qrscanner			scan-or-manual
	User Action	Click"Back" from the UI	INTERACT	onboarding	User	select-back	ui		scan-or-manual
	User Action	Click"Back" from device	INTERACT	onboarding	User	select-back	device		scan-or-manual
	User Action	User selects category (eg: Board) (Total terms shown)	INTERACT	onboarding	User	select-category			scan-or-manual		<category> (CountBoard)	<Total term count>
	User Action	User selects term (eg: AP)	INTERACT	onboarding	User	select-attribute			popup-category	scan-or-manual	<category> (Board)	<term> (Eg: State (Andhra Pradesh) )
	User Action	User clicks on submit for category	INTERACT	onboarding	User	select-submit			popup-category	scan-or-manual	<category>(Medium,Class)	<selected terms>(eg:English/"Class 3, Class 4")
	User Action	User clicks on cancel for category	INTERACT	onboarding	User	select-cancel			popup-category	scan-or-manual	<category>(Medium,Class)	<selected term>(eg:English/"Class 3, Class 4")

<Use Case 1 Overall Process Workflow>

Wireframes

N/A

For Future Release

Yes

JIRA Ticket ID

Localization Requirements

N/A

Non-Functional Requirements

N/A

Impact on other Products/Solutions

NO

Impact on Existing Users/Data

User/Data Impacted	Impact Description

Key Metrics

Srl. No.	Metric	Purpose of Metric

ETB User Actions, System Response, Telemetry Mapping

Introduction

JTBD

Requirement Specifications

Telemetry Requirements

<Use Case 1 Overall Process Workflow>

Wireframes

For Future Release

JIRA Ticket ID

Localization Requirements

Non-Functional Requirements

Impact on other Products/Solutions

Impact on Existing Users/Data

Key Metrics