Requirements were gathered during interviews and conversations with the end users and the Product Owner. The functional requirements for the new system are much the same as those for the current system. Most observations from the end users concerned non-functional requirements.
The functional and non-functional requirements are specified below.
The next step will be to translate these requirements into:
EPICs - large functional requirements that deliver areas of functionality that is completed within the project. EPICs contain Features.
Features - smaller functional requirements that deliver areas of functionality that is completed within an increment (4-12 weeks). Features contain User Stories.
User Stories - smaller functional requirements that deliver areas of functionality that is completed within a Sprint (2 weeks). User Stories contain Tasks. Task breakdown of User Stories will take place during Backlog Refinement meetings during Sprints once the project team is assembled.
Themes - deliver cross cutting elements of the project; usually non-functional requirements.
Requirements from Current System
To be completed
Requirements from User Research During Evaluation
Requirement 1
A service that doesn't crash | |
|---|---|
As a | Revalidation Administrator |
I Want | a reliable service that doesn't crash all the time |
So that | I can do my work without the frustration of an unreliable system |
MoSCoW | |
Priority | |
Notes | I saw the system crash twice at Thames Valley and once at West Midlands, so this is not an infrequent occurrence. |
0 Comments