Scribd
Upload
1K views1 page

Agile & Scrum Cheat Sheet

The document defines key terms used in Scrum, including backlog, release plan, release, burn up chart, velocity, story, feature/theme, taskboard, Scrum Master, team, story points, and impediment. It describes the Scrum Master as owning the process and leading the team by empowering them and removing impediments. The team is a cross-functional group working together to complete stories. The Product Owner is one person accountable for the backlog and prioritizing stories.

Uploaded by

ozukecalo
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
1K views1 page

Agile & Scrum Cheat Sheet

The document defines key terms used in Scrum, including backlog, release plan, release, burn up chart, velocity, story, feature/theme, taskboard, Scrum Master, team, story points, and impediment. It describes the Scrum Master as owning the process and leading the team by empowering them and removing impediments. The team is a cross-functional group working together to complete stories. The Product Owner is one person accountable for the backlog and prioritizing stories.

Uploaded by

ozukecalo
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

Glossary

BACKLOG: one list containing all stories


RELEASE PLAN: rough schedule of iterations
RELEASE: moving 'Done' stories to production
BURN UP CHART: demonstrates visually how many
points the team got 'Done'
VELOCITY: how many points the team got 'Done' in
an iteration.
STORY: a description of a small valuable customer
requirement
FEATURE/THEME: grouping of related stories
TASKBOARD: where the team tracks their tasks
visibly.
SCRUM MASTER: owns the process, leads the team
by empowering them, removes impediments,
tracks progress.
TEAM: cross-functional group working together to
get a story 'Done'.
STORY POINTS: a relative measure of complexity
for a story.
IMPEDIMENT: anything stopping progress on a
task.

Who is The Team?

Who is The Product Owner?

Who is The ScrumMaster?

Accountable for the


Process
Builds empowered self
organizing teams
Is a Servant Leader
Removes impediments
Creates visibility,
measurement,
accountability and fun
Strong facilitator
Encourages collaboration
and open communication

One Person , accountable


for Backlog and Scope
Prioritizes the backlog
Communicates the Vision
of the product
Defines conditions of
satisfaction
Accepts/rejects stories
Accountable for project
success
Accountable for ROI
Helps define 'Done'
Solicits Customer and
Stakeholders feedback

Cross-functional team
accountable for
delivering business
value iteratively
Engaged, Motivated,
Self Organizing,
Collaborative
Commits to work
Inspects & Adapts
Plans and re-plans
Delivers 'Done' stories
each iteration
Uses TDD, Automation
and Best Practices

The Iteration/Sprint Cycle

Update
Product
Backlog

Iteration
Retrospective

Product
Owner

How
Process

Technical
Lead

Iteration
Planning

Daily Stand
Up

Increments
of 'Done'
work

The TEAM

Scrum
Master

Story Format: As a <role>, I want to <action> so that <value>.

A Story Should Be:

Story Points

Understandable

Independent

Negotiable
Valuable

Iteration
Review
/Demo

What

Estimatable
Small
Testable

3
5
8
13

You might also like