About user stories
User stories are written as tickets with type story.
A good story is:
- Independent: minimal dependencies between stories
- Negotiable: they are not contracts, but can be commented and refined
- Valuable to users
- Estimatable: developers can estimate the amount of work the story requires
- Small: can be implemented in 1-2 weeks (larger stories are Epics)
- Testable: can be verified with an automated test (not a unit test, though)
User stories should not be too detailed. The customer (or product owner) can provide the details when implementation in starting (=when the enhancement ticket is being written).
Read about user stories from Wells, D. (1999). Extreme Programming: A gentle introduction.
An example user story from Fle3 project: http://hilbert.uiah.fi:9673/fle3docs/003_participating_in_kb.html