-
Notifications
You must be signed in to change notification settings - Fork 2
User story 101
So we missed a requirement (not surprising) and you need to add another story to the backlog. Here are things to keep in mind when writing a story:
- Use the provided "Feature Request" template when adding a new issue
- Write the user statement in plain English (if possible), limit technical jargon
- Fill in any technical requirements in the issue description, include screenshots when possible
- Add the appropriate labels (including story sizing) and assign it to the relevant sprint + project + milestone
Stories should be sized according to the Fibonacci sequence:
1: A trivial change (variable renaming, string modification, etc.), something that doesn't touch the database and/or adding/modifying tests
2: A simple change that includes some new code, simple tests, a small attribute added to the UI, etc.
3: A medium change that includes new code, multiple tests with various scenarios, new UI pages, talking to the database, etc.
5: A large change that includes many new files, numerous test cases, new UI pages, structural changes to the database, etc.
Stories that are sized at a 5 should be worked on in groups of 2 or more people, or broken down further!