SCRUM in Brief: All Rights Reserved © Alcatel-Lucent 2012 1

SCRUM in Brief
All Rights Reserved Alcatel-Lucent 2012
Agile Manifesto Philosophy

www.agilemanifesto.org
Individuals and interactions

Working software
over
Process and tools Comprehensive documentation
over
Customer collaboration
Responding to change
over
Contract negotiation
Following a plan
over
SCRUM The Framework
Sprints
Scrum projects make progress in a series of sprints
Analogous to Extreme Programming iterations
Typical duration is 24 weeks or a calendar month at most A constant duration leads to a better rhythm Product is designed, coded, and tested during the sprint
Scrum framework
Roles
Product owner ScrumMaster Team
Ceremonies
Sprint planning Sprint review Sprint retrospective Daily scrum meeting

Artifacts
Product backlog Sprint backlog Burndown charts

Scrum framework
Roles
Ceremonies

Artifacts

Product owner

Define the features of the product Decide on release date and content
Be responsible for the profitability of the product

Prioritize features according to market value Adjust features and priority every iteration, as needed
Accept or reject work results
The ScrumMaster

Represents management to the project Responsible for enacting Scrum values and practices Removes impediments Ensure that the team is fully functional and productive Enable close cooperation across all roles and functions Shield the team from external interferences
The team

Typically 5-9 people
Cross-functional:
Programmers, testers, user experience designers, eventually product owner etc. May be exceptions (e.g., database administrator) Ideally, no titles but rarely a possibility
Members should be full-time

Teams are self-organizing
Membership should change only between sprints
Scrum framework
Roles

Ceremonies

Artifacts

Team capacity Product backlog Business conditions Current product Technology
Sprint planning meeting

Sprint prioritization
Analyze and evaluate product backlog Select sprint goal
Sprint goal
Sprint planning
Decide how to achieve sprint goal (design) Create sprint backlog (tasks) from product backlog items (user stories / features) Estimate sprint backlog
Sprint backlog
Sprint planning
Team selects items from the product backlog they can commit to completing Sprint backlog is created and put on taskboard
Tasks are identified and each is estimated (1-16 hours) Collaboratively, not done alone by the ScrumMaster
High-level design is considered
As a vacation planner, I want to see photos of the hotels.
Code the middle tier (8 hours) Code the user interface (4) Write test fixtures (4) Code the foo class (6) Update performance tests (4)
The sprint goal
A short statement of what the work will be focused on during the sprint
Life Sciences Database Application
Support features necessary for population genetics studies.
Make the application run on SQL Server in addition to Oracle.
Watermill - Hercules
Fix Rollout and implement backward compatibility with Aurora release.
The daily Scrum

Parameters
Daily 15-minutes Stand-up Whole world is invited
Not for problem solving

Only team members, product owner, can talk
Helps avoid other unnecessary meetings
Everyone answers 3 questions

What did you do yesterday?
What will you do today? Is anything in your way?
1
2
These are not status for the ScrumMaster

They are commitments in front of peers
The sprint review (demo)
Team presents what it accomplished during the sprint Typically takes the form of a demo of new features or underlying architecture Informal
2-hour prep time rule No slides
Whole team participates Invite the world
Sprint retrospective

Periodically take a look at what is and is not working Typically 1530 minutes Done after every sprint Whole team participates
ScrumMaster Product owner Team Possibly customers and others
Start / Stop / Continue
Whole team gathers and discusses what theyd like to:
Start doing
Stop doing
Continue doing
Scrum framework
Roles
Ceremonies

Artifacts

Product backlog
The requirements A list of all desired work on the
project Ideally expressed such that each item has value to the users or customers of the product Prioritized by the product owner Reprioritized at the start of each sprint
This is the product backlog
Sprint backlog
Individuals sign up for work of their own choosing
Work is never assigned by a person to another person
Estimated work remaining is updated daily Any team member can add, delete or change the sprint backlog Work for the sprint emerges
If work is unclear, define a sprint backlog item with a larger amount of time and break it down later
Update work remaining as more becomes known
Burndown Charts
Release burn-down chart after each sprint closure
140 121,5 120 100 101,5 88,5 80 71,5 60 Initial release burndown 55,5 45,5 40 22,5 Actual release burndown
20
0 -10,5 -20 Sprint1 Sprint2 Sprint3 Sprint4
Sprint burn-down chart

250
200
Remaining Hours
150
100
50
0 15-Dec 16-Dec 17-Dec 18-Dec 21-Dec 22-Dec 23-Dec
4-Jan
5-Jan
6-Jan
7-Jan
8-Jan 11-Jan 12-Jan 13-Jan 14-Jan 15-Jan 18-Jan 19-Jan 20-Jan 21-Jan 22-Jan 25-Jan 26-Jan
22

SCRUM in Brief: All Rights Reserved © Alcatel-Lucent 2012 1

Uploaded by

Copyright:

Available Formats

SCRUM in Brief: All Rights Reserved © Alcatel-Lucent 2012 1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SCRUM in Brief: All Rights Reserved © Alcatel-Lucent 2012 1

Uploaded by

Copyright:

Available Formats

SCRUM in Brief

All Rights Reserved Alcatel-Lucent 2012

Agile Manifesto Philosophy

Individuals and interactions

Process and tools Comprehensive documentation

All Rights Reserved Alcatel-Lucent 2012

SCRUM The Framework

All Rights Reserved Alcatel-Lucent 2012

Scrum projects make progress in a series of sprints

Analogous to Extreme Programming iterations

Product owner ScrumMaster Team

Sprint planning Sprint review Sprint retrospective Daily scrum meeting

Product backlog Sprint backlog Burndown charts

Product owner ScrumMaster Team

Sprint planning Sprint review Sprint retrospective Daily scrum meeting

Product backlog Sprint backlog Burndown charts

Be responsible for the profitability of the product

Accept or reject work results

All Rights Reserved Alcatel-Lucent 2012

All Rights Reserved Alcatel-Lucent 2012

Members should be full-time

Membership should change only between sprints

All Rights Reserved Alcatel-Lucent 2012

Product owner ScrumMaster Team

Sprint planning Sprint review Sprint retrospective Daily scrum meeting

Product backlog Sprint backlog Burndown charts

Team capacity Product backlog Business conditions Current product Technology

Sprint planning meeting

Analyze and evaluate product backlog Select sprint goal

All Rights Reserved Alcatel-Lucent 2012

High-level design is considered

As a vacation planner, I want to see photos of the hotels.

All Rights Reserved Alcatel-Lucent 2012

The sprint goal

Make the application run on SQL Server in addition to Oracle.

The daily Scrum

Not for problem solving

Helps avoid other unnecessary meetings

All Rights Reserved Alcatel-Lucent 2012

Everyone answers 3 questions

These are not status for the ScrumMaster

The sprint review (demo)

Whole team participates Invite the world

All Rights Reserved Alcatel-Lucent 2012

All Rights Reserved Alcatel-Lucent 2012

Start / Stop / Continue

Whole team gathers and discusses what theyd like to:

All Rights Reserved Alcatel-Lucent 2012

Product owner ScrumMaster Team

Sprint planning Sprint review Sprint retrospective Daily scrum meeting

Product backlog Sprint backlog Burndown charts

This is the product backlog

All Rights Reserved Alcatel-Lucent 2012

Individuals sign up for work of their own choosing

Work is never assigned by a person to another person

All Rights Reserved Alcatel-Lucent 2012

0 -10,5 -20 Sprint1 Sprint2 Sprint3 Sprint4

Sprint burn-down chart

0 15-Dec 16-Dec 17-Dec 18-Dec 21-Dec 22-Dec 23-Dec