Skip to content

Template: Requirements page

James K. Glasbrenner edited this page Nov 10, 2019 · 1 revision

Requirements page template

The following template was put together using the following resources:


Target release MM/DD/YYYY
Epic ID of associated epic
Document maintainer Name

Background

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?

Success metrics

List the goals and metrics to be used for measuring progress.

Goal Metric

Assumptions

List any assumptions about the intended use cases, technical constraints, or user expectations.

User stories

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

User interface and design

If applicable, add mockups, diagrams, or visual designs related to the requirement.

Open questions

List the things that need to be decided or researched for the requirement.

Out of scope

If applicable, list anything that's out of scope for this requirement.

Table of contents

sPyns architecture

Templates

Clone this wiki locally