Professional Documents
Culture Documents
Glossary The Iteration/Sprint Cycle Story Format: ‘As a <role> I want to <action> so that
<value>
BACKLOG: one list containing all stories Story Points
A Story Should Be:
RELEASE PLAN: rough schedule of iterations
RELEASE: Moving 'Done' stories to production 1
❖ Understandable
BURN UP CHART: demonstrates visually how many Update
points the team got 'Done' Iteration
Product
VELOCITY: how many points the team got 'Done' in Planning ❖ Independent 2
Backlog
an iteration.
STORY: a description of a small valuable customer ❖ Negotiable 3
requirement
FEATURE/THEME: grouping of related stories Iteration Daily Stand ❖ Valuable
TASKBOARD: where the team tracks their tasks Retrospective Up 5
visibly.
SCRUM MASTER: owns the process, leads the team ❖ Estimatable
by empowering them, removes impediments, tracks
progress. Iteration Increments 8
❖ Small
TEAM: cross-functional group working together to Review of 'Done'
get a story 'Done'. /Demo work
STORY POINTS: a relative measure of complexity for ❖ Testable
a story. 13
IMPEDIMENT: Anything stopping progress on a task.