-
Notifications
You must be signed in to change notification settings - Fork 2
Template: Requirements page
The following template was put together using the following resources:
- Atlassian Agile Coach - Product requirements documents, downsized
- Atlassian Agile Coach - User Stories | Examples and Template
- Atlassian Confluence - Product requirements document template
Target release | MM/DD/YYYY |
Epic | ID of associated epic |
Document maintainer | Name |
Provide context for this project requirement. Some questions to consider are,
- Why is this requirement necessary?
- How does this requirement fit into the overall project objectives?
List the goals and metrics to be used for measuring progress.
Goal | Metric |
---|
List any assumptions about the intended use cases, technical constraints, or user expectations.
Express the high-level tasks that need to be completed in the form of user stories, which should articulate how value will be delivered to the intended user—the term user is broadly defined—upon completion of each task. Each story should be, at most, a few sentences long, written in simple language, and articulate the desired outcome.
User story title | User story description | Priority | Notes |
---|
If applicable, add mockups, diagrams, or visual designs related to the requirement.
List the things that need to be decided or researched for the requirement.
If applicable, list anything that's out of scope for this requirement.