Agile User Stories
Jump to navigation
Jump to search
Notes from the excellent book User Stories Applied [1] ISBN 0321205685
Writing User Stories
Good stories : INVEST
- Independent
- Negotiable
- Valuable to users
- Estimable
- Small
- Testable
Dependencies
- Combine stories
- Split in a different way
- 2 Estimates - one before and one after dependent story
Negotiable
- Short description - details negotiable
- Important details annotated
- include undecided info as a prompt to resume discussion
- Avoid excessive detail - consider separate card - details become tests
- User stories for all stakeholders
- Avoid developer stories - reword in user context with user value
- Avoid user interface/assumptions/technology
Estimation
Problems:
- lack of domain knowledge
- discuss until general understanding reached
- lack of technical knowledge
- run technical spike - time box - experiment to learn enough to be able to estimate
- story too big
Types of user stories
Epic
Big picture
Story
- Description for planning - card
- Conversations for gasthering detail - conversation
- Tests determine when complete - confirmation
Should be written in business language - domain
Prioritisation
- How desirable to all users
- How desirable to subset of users
- Cohesiveness to other stories
- Cost
Adjust requested by developers
- Technical risk
- Complementary to other stories
Acceptance tests
Tests documented as soon as possible
User Stories
- Emphasis the verbal
- Comprehensible by the user + dev
- sized for planning
- supports iterative development
- defers detail until it is required
- something the user would do in a single sitting
Stories are epics until prioritised
- Differed stories
- Iteratively refined