STORY TITLE
- syntax:
<subject><verb><object>[modifier] - Subject: author, admin, developer, reader, visitor, editor, approver, user
- Verb: always in the present tense: creates, clicks, sees, sends
- Object: terminology / informal entities: message, payment info, work order
- modifier: optional, must add relevant detail, keep to a minimum
STORY DESCRIPTION
- includes the motivation of the feature
- the acceptance criteria
POINTS (Fibonacci Style)
- 1 Pts: story takes an hour or two
- 2 Pts: story takes the morning
- 3 Pts: story takes the whole day
- 5 Pts: story takes more than one day
- 8 Pts: too much complexity, needs to be broken down and scheduled further
- workers estimate points not managers points can't be changed once story is started
LABELS
- usually refer to a component or a system
- sample labels: CMS, registration, onboarding, checkout, reporting
- more than one label is alright, two is common, three is rare
TASKS
- developer oriented lists of things to be done in order to deliver the story coder talk goes here
BUGS
- stories without points
- usually from support tickets, project owner, testers
CHORES
- stories that don't deliver value to the user
- setup servers, get content approval