1
Q
Categories of requirement
A
- Business - General (rules) & Technical (constrainsts) [policy requirements all projects have to adhere to]
- Solution - functional (what system will do) & non functional (how well system will do it)
2
Q
Well constructed user story - INVEST
A
I - Independant
N- negotiable
V - Valuable
E - Estimable
S - Small
T - testable
3
Q
User Story card: Front details
A
- Unique identifier
- Story title
- Role - ‘As a’
- Requirement problem ‘I want’
- Business value derived ‘So that’
4
Q
User Story Card: Back
A
- Acceptance criteria - High level can be questions. Low level - GIVEN, WHEN, THEN
- NFR’s
5
Q
User story - card - 3 C elements
A
- Card
- Conversation
- Confirmation
6
Q
How to visualise user stories
A
- Story Maps
- Impact mapping
