User Stories Specification Template

Documentation / Get Started

This requirements specification template helps with describing high-level needs of product stakeholders as agile user stories.

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.

For more information see User Stories Applied by Mike Cohn or his User Stories web page.

Template Instructions

If you create a new document from this template (see Create Documents) then the application displays detailed guidance in the Instructions pane:

Instructions from the User Stories document template


IdidstringUnique identifier within the document
HeadingheadingstringShort name of the user story
As a(n)asAnenumType of user
I want toiWantxhtmlGoal of the user story
So thatsoThatxhtmlReason the user story
Acceptance CriteriaacceptanceCriteriaxhtmlMore details how the story should be verified and providing the basic criteria that can be used to determine if a story is fully implemented
PrioritypriorityenumPriority assessment of the user story — High, Medium, or Low
RiskriskenumRisk assessment of the user story — High, Medium, or Low
EstimationestimationintThe relative user story complexity, effort or duration estimated by story points
StatusstatusenumStatus of the user story supporting your workflow
TypetypeenumType of the document object — Section, Information, Epic, User Story or Constraint


Check NEEDS document in the Example Project describing User Stories.


 Try ReqView
Updated for version 2.18.2