Scrum

Definition & Theory

framework

lightweight

simple to understand

difficult to master

to address complex adaptive problems

deliver products

process

iterative

incremental

empirical

transparency

inspect

adapt

< pillars

specific tactics may vary not part of the guide

based on Scrum Guide

July @ABC

byKen Schwaber

Jeff Sutherland

Rules

Product Backlog Refinement

Artifact Transparency

Monitoring Progress

I Scrum Values

commitment

courage

focus

openness

respect

< Artifacts

Product Backlog

Sprint Backlog

Increment

to provide transparency

B or many Scrum Team (s)

< roles

self-organizing

cross-functional

optimizes

flexibility

creativity

productivity

to deliver product

I Events

Sprint

Sprint Planning

Daily Scrum

Sprint Review

Sprint Retrospective

inspect & adapt loops

www.qagile.pl

Scrum

Definition & Theory

Rules

Product Backlog Refinement

act of

adding detail

estimating

ordering

ongoing process

Product Owner and the Development Team collaborate on the details

Scrum Team decides how and when is done

consumes no more than >?% of the capacity

Artifact Transparency

Scrum Masterworks to increase

can detect incomplete

it's a path

Definition of Done

Scrum Team specific

to ensure transparency

work is complete

shared understanding

of what Done means

of potentially releasable

between multiple Scrum Teams working on the same Product

expands as Scrum Teams mature

starts from

conventions

standards

guidelines

Monitoring Progress

toward a Goal

Product Owner tracks

work remaining can be summed

at least every Sprint Review

transparent to all stakeholders

of the Sprint

Developemtn Team tracks

work remaining can be summed

at least every Daily Scrum

likehood of achieving the Sprint Goal

various practices

burn-down

burn-up

cumulative flow

other

importance of empiricism

H Scrum Values

J Artifacts

> or many Scrum Team (s)

H Events

www.qagile.pl

Scrum

Definition & Theory

Rules

2 Scrum Values

8 Artifacts

Product Backlog

list

ordered

dynamic

evolves

changesanytime

at Product Owner discretion

of

features

functions

requirements

enhancements

fixes

Product Backlog Items

description

order

estimate

value

never complete

exists as long as the product

single sourceof requirements

for multiple teamsgrouping attribute might be added

needs refinementhigher ordered items

more clear

more precise estimate

Ready Product Backlog itemscan be selected for the next Sprint

Sprint Backlog

forecastchanged

as needed

during the Sprint

only by Development Team

set of

Product Backlog Itemsselected for the Sprint

plan of work

of delivering the PBIs

next daysdecomposedin units of workG day or less

for the Sprint

highly visible

real-time

remaining work updated

elements removed

work emerges

detailedenough for Daily Scrum

belongs to the Development Team

Increment

must be Done

according to the Definition of Done

usable condition

tested

integrated with previous Increments

sumall Product Backlog Itemsdone in this Sprint

increments of all previous Sprints

releasedwhen Product Owner decides

to provide transparency

G or many Scrum Team (s)

2 Events

www.qagile.pl

Scrum

Definition & Theory

Rules

2 Scrum Values

8 Artifacts

: or many Scrum Team (s)

8 roles

Product Owner

responsible for

Product Backlog management

clearly expressing Product Backlog items

ordering the items

optimizing the value of the work

Product Backlog is visible

Development Team understands items

Return on Investment

Total Cost of Ownership

may have Development Team to do it

one person

not a commitee

representsstakeholders

decision making

NOTScrum Master

Development Team

self-organizing

cross-functional

responsible for

maximizingopportunitiesfor feedback

doing the work

iteratively

incrementally

creatingIncrementpotentially shippable

done

estimation

organizację pracy

consists of

professionals

Developers

od 8 do Padvised size

counting all who do the work

can have area of focus

all accountablefor the result

no sub-teams

Scrum Master

responsible for Scrumunderstood

enacted

process manager"management position"

servant-leader

serves

Product Owner

Product Backlog management

empirical planning

maximizing value

undestanding agility

facilitating Scrum events

Development Team

coaching

helping

removing impediments

facilitating events

organization

Scrum adoption

planning implementation

empirical product development

causing change

working with other Scrum Masters

NOTProduct Owner

self-organizing

cross-functional

optimizes

flexibility

creativity

productivity

to deliver productincrementally

iterativelymaximizing feedback opportunities

2 Events

www.qagile.pl

Scrum

Definition & Theory

Rules

2 Scrum Values

8 Artifacts

: or many Scrum Team (s)

2 Events

Sprint

time-box

: calendar month or less

constant duration

no breaks in between Sprints

hard

can be cancelled

by Product Ownercan be influenced by others

when the Sprint Goal is obsolete

effect

traumatic for the team

consumes resources

Product Backlog Items

Donereviewed with Product Owner

un-Donere-estimated

put back to the Product Backlog

but rarely makes sense

rules

no changes

influencing the Sprint Goal

quality goals

team composition

scopecan be clarifiedas more is learned

re-negotiatedbetween the Product Owner and Development Team

my be considered as a project

the heart of Scrum

container forother events

the development work

Sprint Planning

Daily Scrum

Sprint Review

Sprint Retrospective

inspect & adapt loops

www.qagile.pl

Scrum

Definition & Theory

Rules

2 Scrum Values

8 Artifacts

: or many Scrum Team (s)

2 Events

Sprint

Sprint Planning

time-box

Bhfor : month Sprint

usually shorterfor shorter Sprints

maximal

input

Product Backlog

last Increment

Development Team'sprojected capacity

past performance (velocity)

purpose

what can be delivered?

Product Ownerdiscussesthe objective

Product Backlog Itemsneeded to achieve the objective

Development Teamcreates a forecast

The Scrum Teamcrafts the Sprint Goal

how can it be achieved?

Development Team

creates the Sprint Backlog

may invite other peopleto provide knowledgetechnical

business

Product Ownerclarifies PBIs

renegotiates the scope

outputSprint Goal

coherent function

coherent cause to work together

Sprint Backlog

Daily Scrum

Sprint Review

Sprint Retrospective

inspect & adapt loops

www.qagile.pl

Scrum

Definition & Theory

Rules

2 Scrum Values

8 Artifacts

: or many Scrum Team (s)

2 Events

Sprint

Sprint Planning

Daily Scrum

time-box:2 minutes

maximal

purpose

synchronize activities

create a plan for next DEh

inspect progress towards the Sprint Goal

optimize probabilityto meet the Spring Goal

rules

same time and place

each day

8 questions

What did I do yesterday that helped the Development Team meet the Sprint Goal?

What will I do today to help the Development Team meet the Sprint Goal?

Do I see any impediment that prevents me or the Development Team from meeting the Sprint Goal?

responsibility

Development Teamconducts the meeting

Scrum Master

ensures the meeting takes place

ensures only Development Team members participate

teaches to keep the time-box

discussionsimmediately after the meeting

key inspect & adapt meeting

NOTstatus meeting

Sprint Review

Sprint Retrospective

inspect & adapt loops

www.qagile.pl

Scrum

Definition & Theory

Rules

2 Scrum Values

8 Artifacts

: or many Scrum Team (s)

2 Events

Sprint

Sprint Planning

Daily Scrum

Sprint Review

time-box

Bhfor : month Sprint

usually shorterfor shorter Sprints

maximal

purpose

inspect the Increment

adapt the Product Backlog if needed

valuable input to subsequent Sprint Planning

rules

attendeesScrum Team

key stakeholdersinvited by the Product Owner

Scrum Master

ensures the event takes place

teaches allto keep timebox

the purpose

Development Team

discusses

what went well during the Sprint

what problems it ran

how those problems were solved

demonstrates the Done work

answers questionsabout the Increment;

Product Owner

The Product Owner discusses the Product Backlog as it stands. He or she projects likely

completion dates based on progress to date (if needed);

The Product Owner explains what Product Backlog items have been “Done” and what has

not been “Done”;

the whole group reviews

what to do nextthe most valuable thing

for the next release

timeline

budget

potential capabilities

marketplace

potential use of the product

presentation of the Incrementto get feedback

outputrevised Product Backlogprobable Product Backlog items for the next Sprint

new opportunities

NOTstatus meeting

demo

Sprint Retrospective

inspect & adapt loops

www.qagile.pl

Scrum

Definition & Theory

Rules

2 Scrum Values

8 Artifacts

: or many Scrum Team (s)

2 Events

Sprint

Sprint Planning

Daily Scrum

Sprint Review

Sprint Retrospective

time-box

8hfor : month Sprint

usually shorterfor shorter Sprints

maximal

after the Sprint Review

prior to the next Sprint Planning

purpose

to inspect last Sprint

people

relationships

process

tools

to make the next Sprintmore effective

more enjoyable

increase product qualityadapting the Definition of Done

create a plan for improvementsto be enacted during the next Sprint

Scrum Master

ensures the event takes place

teaches allto keep timebox

the purpose

participatesas team member

from the accountability over the Scrum process

output identified improvementsto implement in the next Sprint

inspect & adapt loops

www.qagile.pl