20
1 Scrum Process

Scrum Process

Embed Size (px)

Citation preview

1

Scrum Process

Agenda

n  Introduction

n  Overview

n  Scrum Frameworkn  Rolesn  Ceremoniesn  Artifacts

2

3

What is Scrum?

n  Scrum is an agile

n  Rapidly and Repeatedly release software

n  The business sets the priorities

n  Iterative Process

Mountain Goat Software, LLC4

Companies that Use Scrum

§  Microsoft§  Yahoo§  Google§  Electronic Arts§  High Moon Studios§  Lockheed Martin§  Philips§  Siemens§  Nokia§  Capital One§  BBC§  Intuit

§  Intuit§  Nielsen Media§  First American Real

Estate§  BMC Software§  Ipswitch§  John Deere§  Lexis Nexis§  Sabre§  Salesforce.com§  Time Warner§  Turner Broadcasting§  And many others

5

Scrum Characteristics

n  Self-organizing teams

n  Product progresses in a series of short periods “sprints”

n  Requirements are captured as items in a list of “product backlog”

n  No specific engineering practices prescribed

n  One of the “agile processes”

Source: www.agilemanifesto.org 6

What is it about?

Process and tools Individuals and interactions

over

Following a plan Responding to change over

Comprehensive documentation

Working software over

Contract negotiation Customer collaboration

over

Source: www.mountaingoatsoftware.com/scrum 7

Overview

Source: www.mountaingoatsoftware.com/scrum 8

Scrum Framework

• Product owner • Scrum master • Team

Roles

• Sprint planning • Sprint review • Sprint retrospective • Daily scrum meeting

Ceremonies

• Product backlog • Sprint backlog • Burndown charts

Artifacts

Product Owner

n  Defines the features of the product

n  Decides on release date and content

n  Prioritizes features according to market value

n  Adjusts features and priority every iteration 

n  Accepts or rejects work results

The Scrum Master

n  Represents management to the project

n  Removes impediments

n  Ensures that the team is fully functional and productive

n  Shields the team from external interference

The Team

n  Typically 5-9 people

n  Cross-functional:•  Programmers, testers, user experience designers...

n  Teams are self-organizing•  Ideally, no titles but rarely a possibility

n  Membership should change only between sprints

• Product owner • Scrum master • Team

Roles

Scrum Framework

• Product backlog • Sprint backlog • Burndown charts

Artifacts

• Sprint planning• Sprint review• Sprint retrospective• Daily scrum meeting

Ceremonies

Source: www.mountaingoatsoftware.com/scrum

Sprint planning meeting

Sprint prioritization

•  Analyze and evaluate product backlog

•  Select sprint goal

Sprint planning

•  Decide how to achieve sprint goal

•  Create sprint backlog from product backlog items (user stories / features)

•  Estimate sprint backlog in points/hours

Sprintbacklog

Team capacity

Product backlog

Current product

Source: www.mountaingoatsoftware.com/scrum

The Daily Scrum

n  Daily 15-minutes Stand-up meeting

n  Not for problem solving

n  Answer 3 Questions•  What did you do yesterday?•  What will you do today?•  Is anything in your way?

The Sprint Review

n  Team presents what it accomplished during the sprint

n  Typically takes the form of a demo of new features

n  Whole team participates

n  Invite the world

Sprint Retrospective

n  Periodically take a look at what is and is not working

n  Typically 15–30 minutes

n  Done after every sprint

n  Whole team participates

• Product owner • Scrum master • Team

Roles

Scrum Framework

• Sprint planning • Sprint review • Sprint retrospective • Daily scrum meeting

Ceremonies

• Product backlog• Sprint backlog• Burndown charts

Artifacts

Source: www.mountaingoatsoftware.com/scrum

Product Backlog

n The requirements

n A list of all desired work on the project

n Prioritized by the product owner

n Reprioritized at the start of each sprint

A sample product backlogBacklog item Complexity

Allow a guest to make a reservation 2

As a guest, I want to cancel a reservation. 5

As a guest, I want to change the dates of a reservation. 2

As a hotel employee, I can run RevPAR reports (revenue-per-available-room) 8

Improve exception handling 8... 40... 80

Poi

nts

40

30

20

10

0 Mon Tue Wed Thu Fri

50

Burndown Charts