<The things to be entered are already mentioned clearly. Ideally, this should be one single page for all the requirements from the stakeholders and a confirmation in comments by the key stakeholder. If there are multiple deliverable, ensure that there are separate pages with right headings.>


Target releaseRelease name or number
EpicLink to related JIRA epic or feature
Document status
Document owner

Mukul Pati Singh

DesignerLead designer
DevelopersLead developer
QALead tester


Goals

Background and strategic fit

Why are you doing this? How does this relate to your overall product strategy?

Assumptions

Requirements

#TitleUser StoryImportanceNotes
1Short identifier for the storyDescribe the user and what they are trying to achieveMust Have
  • Additional considerations or noteworthy references (links, issues)
2    

User interaction and design

Include any mockups, diagrams or visual designs relating to these requirements.

Questions

Below is a list of questions to be addressed as a result of this requirements document:

QuestionOutcome
(e.g. How we make users more aware of this feature?)Communicate the decision reached

Not Doing