Login
RegisterTemplate of backlog's requirements (User story for Agile method)
Version: 1.0Date: 2021/01/06
Introduction
Purpose
This document explains the shape that the requirements must take to form a backlog.Stakeholders
| Responsible | Accountable | Consulted | Informed |
|---|---|---|---|
| Product Owner | Product Owner | Users | Project Team |
Versions
| Version | Date | Author | Description |
|---|---|---|---|
| 1.0 | 2021/01/06 | Emeline Robert Aubrun @manageprojects.tech | Initialization |
Input
| Document | Version | Link | Description |
|---|
Requirements or backlog
Backlog is the list of stories ordered by value/priority. 2 stories can't have the same priority.The story on top will be first done.
With this method, the requirements with the most value will be done first and if there is not enough time, the most valuable will be done first.
Story
Description
Priority: ranking of the need in the backlog that determines its order of realization. The priority must take into account the value for the customer but also early remove doubt about feasability.As ...(user/administrator/customer/member) ...
I can ...(action) ....
To ...(gain for the user)...
Acceptance Criteria
The action must be performed.The data are stored in the database.
The action is logged.
The xxx page is displayed with a confirmation message.
Other users cannot initiate the action.
Attached Files
Mock-up of the screens.Tests' plan.