Method wall › Artifacts & Metrics
Artifacts & Metrics
Method cards filed under Artifacts & Metrics.
Artifacts & Metrics
The Product Backlog Is a Living List Not a Contract
CeremonyBacklog refinement, sprint planning, daily scrum, sprint review, and sprint retrospective are the recurring ceremonies most closely associated with a Scrum-based product backlog.
RolesThe product owner owns ordering and clarity of the backlog; developers pull and deliver items; a scrum master or coach supports the process and removes impediments.
ArtifactsThe product backlog itself, plus sprint backlog, product goal, sprint goal, and the increment produced at the end of a cycle.
CadenceA fixed-length iteration, commonly one to four weeks, with a regular review and retrospective rhythm.
The product backlog is often described as a prioritized list of everything that might improve a product.
Artifacts & Metrics
The Sprint Backlog Belongs to the Team Alone
CeremonySprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective, all contained within a single Sprint; backlog refinement happens as needed rather than as a fixed event.
RolesThe Product Owner orders the Product Backlog and clarifies value; the Scrum Master coaches the process and removes impediments; the Developers self-manage the Sprint Backlog and decide how to do the work.
ArtifactsProduct Backlog, Sprint Backlog, and the Increment, with the Sprint Goal giving the Sprint Backlog its purpose.
CadenceFixed-length Sprints, typically two to four weeks, with a new Sprint starting immediately after the previous one ends.
The Sprint Backlog is the set of work a Scrum team plans to do during a single Sprint, together with the plan for how that work will get done.
Artifacts & Metrics
A Burndown Chart Shows Shape Not Performance Scores
CeremonyDaily coordination meeting, iteration planning, iteration review, retrospective, and backlog refinement sessions
RolesProduct owner, Scrum master, and development team members
ArtifactsProduct backlog, sprint backlog, increment, burndown chart, and definition of done
CadenceTime-boxed iterations, typically one to four weeks, called sprints
A burndown chart is a simple line graph that shows how much work remains in a sprint over time.
Artifacts & Metrics
Velocity Is a Planning Aid Not a Productivity Score
CeremonySprint planning, Daily Scrum, Sprint Review, and Sprint Retrospective form the recurring meeting set; refinement sessions are common but optional.
RolesProduct Owner sets and orders the work; Scrum Master coaches the process and removes impediments; Developers self-manage delivery.
ArtifactsProduct Backlog, Sprint Backlog, and the Increment, with a Definition of Done governing what counts as complete.
CadenceFixed-length sprints, commonly one to four weeks, with a consistent length maintained across sprints.
Velocity is the amount of work a team completes in a fixed period, usually expressed as the sum of estimates attached to items finished during a sprint.