This requirements specification template helps with describing high-level needs of product stakeholders as agile user stories.
User stories are simple statements formulated according to the following structure: “As a <type of user>, I want <some goal>, so that <some reason>.”
You can specify user stories describing functionality of the product grouped into epics for easier navigation in the document.
You can also identify constraints addressing non-functional requirements about product performance, accuracy, portability, reusability, maintainability, interoperability, availability, usability, security and capacity and specify them in the same form as the user stories.
If you create a new document from this template (see Create Documents) then the application displays detailed guidance in the Instructions pane:
|Unique identifier within the document
|Short name of the user story
|Type of user
|I want to
|Goal of the user story
|Reason the user story
|More details how the story should be verified and providing the basic criteria that can be used to determine if a story is fully implemented
|Priority assessment of the user story — High, Medium, or Low
|Risk assessment of the user story — High, Medium, or Low
|The relative user story complexity, effort or duration estimated by story points
|Status of the user story supporting your workflow
|Type of the document object — Section, Information, Epic, User Story or Constraint