Scrum group7 20120213

© BlueChipConsulting.nl

SCRUM Agile software development framework

Carel Aeijelts Averink Online Project/Program Manager

Blue Chip Consulting


Introduction


Organizations

Industries Government Media &

Telecommunications Advertising

Websites www.rijksoverheid.nl www.upc.nl www.detelefoongids.nl

Roles ScrumMaster Program Manager

Online

Program Manager

Marketing Online

Key elements

Content management,

open standards,

accessibility

eCommerce, online

sales, conversion

Content, search, SEO,

high volume traffic

Scrum

In-house Scrum teams

Local Product Owner

Distributed Scrum team

(Veenendaal)

Corporate Product

Owner

Distributed Scrum

teams (Denver, Vienna)

Local Product Owner

Projects using Scrum


Roots of Scrum

Just in Time, Lean,

Kanban

Total Quality Control,

W.Edwards Deming

Scrum


• Scrum is not a

methodology

• Scrum is not a defined

process

• Scrum is not a set of

procedures

Definition of Scrum

The Scrum Guide contains the definition of Scrum. This definition consists of Scrum’s

roles, events, artifacts, and the rules that bind them together

http://www.scrum.org/scrumguides/

• Scrum is an open

development framework with

a simple set of rules

• It has been used to manage

complex product develop-

ment since the early 1990s

• Ken Schwaber and Jeff

Sutherland developed Scrum


The defined process control

model requires that every

piece of work be completely

understood. Given a well-

defined set of inputs, the

same outputs are generated

every time.

Empirical Process Control

Three pillars uphold every implementation of empirical process control:

transparency, inspection, adaptation

http://www.scrum.org/scrumguides/

The empirical process control

model asserts that knowledge

comes from experience and

making decisions based on what

is known. Scrum employs an

iterative, incremental approach

to optimize predictability and

control risk.


Scrum vs. Waterfall

Waterfall Scrum

Fixed Scope & Time Fixed Time & Resources

Central planning,

Gantt Chart

Release Planning

Sprint Planning

Daily Scrum

Change Management Backlog Prioritization

Centrally coordinated teams Self organizing teams

Specialized teams (functional silo’s) Interdisciplinary teams

Documentation Communication


Scrum Static Model

3 Roles 5 Events 3 Artifacts

Product Owner The Sprint Product Backlog

Development Team Sprint Planning Meeting Sprint Backlog

ScrumMaster Daily Scrum (stand-up) Increment

Sprint Review (demo)

Sprint Retrospective

Optional Events

Release Planning

Backlog Grooming

Scrum of Scrums


Scrum Dynamic Model [1]

Source: http://zenagile.files.wordpress.com/2011/09/scrum-lifecycle.jpg


Scrum Dynamic Model [2]

This defines what must be

completed before and after a sprint

• Analysis

• Design

• Development

• Testing

• Deployment

http://blog.xebia.com/2009/06/19/the-definition-of-ready/

READY and DONE


Requirements

Source: http://jamespeckham.com/

Product Owner


User Stories

• Acceptance criteria

• Designs

• Story points

As a .… [product user],

I want …. [product feature],

So that I can …. [benefit/purpose].


Estimation

Estimate on Units Range Precision

Epics Complexity

T-shirt sizes

or

Story Points*

S-XXL

40-100*

low

User Stories Complexity Story Points* 0-20* good

Tasks Effort Hours 2-6 hours high

*Story Points are estimated by

the Team in Planning Poker

Source: www.mountaingoatsoftware.com


Scrum (Task) Board

Source: http://accurev.com/blog/2010/09/27/implementing-agile/

Source: http://blog.xebia.com/2008/09/19/the-task-burn-down-trap-everything-finished-nothing-done/


Burndown Chart

Monitor Predict

Learn Improve


The Team

Source: totallycoolpix.com


ScrumMaster

ScrumM movie


Product Owner

Source: www.flickr.com/photos/minister-president/


Distributed Scrum

Source: www.infoq.com/articles/dutch-railway-scrum


Business Cases

Case 1: Improve the process

Average website development Release cycle: 46 days.

Distributed Scrum by 3rd party vendor: 24 days.

SCRUM SPRINTS BAT PRODUCTION DEPLOYMENT

4 days 18 days 2 days 10 days 12 days

Average 18 days contributed to

software development velocity

Average 10 days for

Business Acceptance

& Regression Testing

Average 12 days for

Deployment & Stage

Regression Testing

DONE READY

Potentially

Shippable In

Production


Points of Attention

• Documentation

• Management buy-in/commitment

• Cultural aspects

• Risk Management

• Release Planning

• Fixed Price


Release Planning

“Any Product Manager that has successfully

delivered a product to a customer knows how

incredibly important Release Planning is.

Despite its importance, the 2011 Scrum Guide,

published in July by Ken Schwaber and Jeff

Sutherland, removes any discussion about

Release Planning and the related Release

Burndown chart.”

From www.scrum.org/scrum-guide-updates


Fixed Price

“Money for nothing and your change for free”

http://jeffsutherland.com/Agile2008MoneyforNothing.pdf


Greenhopper (JIRA/Atlassian)


Links

Scrum training • Jeff Sutherland

http://www.scrumalliance.org/profiles/70-jeff-sutherland-phd

• Ken Schwaber http://courses.scrum.org/about/ken-schwaber

• Mike Cohn http://www.mountaingoatsoftware.com/training-available

Scrum certification http://www.scrumalliance.org/scrum_certification

Scrum User Group Netherlands http://www.meetup.com/nlscrum/


Contact

[email protected]

www.linkedin.com/in/onlineprojectmanager

@carel

Date post:	10-May-2015
Category:	Technology
Upload:	carel-aeijelts-averink
View:	1,327 times
Download:	0 times

Scrum group7 20120213

Technology