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.
For more information see User Stories Applied by Mike Cohn or his User Stories web page.
If you create a new document from this template (see Create Documents) then the application displays detailed guidance in the Instructions pane:
Name | Identifier | Type | Description |
---|---|---|---|
Id | id | string | Unique identifier within the document |
Heading | heading | string | Short name of the user story |
As a(n) | asAn | enum | Type of user |
I want to | iWant | xhtml | Goal of the user story |
So that | soThat | xhtml | Reason the user story |
Acceptance Criteria | acceptanceCriteria | xhtml | 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 | priority | enum | Priority assessment of the user story — High, Medium, or Low |
Risk | risk | enum | Risk assessment of the user story — High, Medium, or Low |
Estimation | estimation | int | The relative user story complexity, effort or duration estimated by story points |
Status | status | enum | Status of the user story supporting your workflow |
Type | type | enum | Type of the document object — Section, Information, Epic, User Story or Constraint |
Check NEEDS document in the Example Project describing User Stories.