Intro to Scrum (shared) 05 2011

Traditional Project Management

Eri

n B

eie

rwa

lte

s |

ag

ile

act

ion

.blo

gsp

ot.

com

How did we do?

Scaling Software Agility – Dean Leffingwell

Erin Beierwaltes | agileaction.blogspot.com

Scrum

Eri

n B

eie

rwa

lte

s |

ag

ile

act

ion

.blo

gsp

ot.

com

The Agile Manifesto

Process and toolsIndividuals and

interactionsover

Following a planResponding to change over

Source: www.agilemanifesto.org

Comprehensive documentation

Working software over

Contract negotiationCustomer collaboration over


Features Used by Customers

Always, 7%

Often, 13%

Sometimes, 16%

Rarely, 19%

Never, 45%

Standish Group Study reported at XP2002 by Jim Johnson, Chairman© Poppendieck LLC


Why Scrum?

Delivering the highest business value in the shortest time

Working software every two to four weeks

Business sets priorities, while teams self-organize for delivery of highest priority features

Reprioritization every two to four weeks or option to release

It’s better to have 80% 100% done, instead of 100% 80% done.


Requirements Game

Get into teams of 2

Choose a Product Manager and a Developer

Developers leave the room

Product Managers write a “design document” for developers

Words ONLY

Developers come back in and try to follow written instructions



PMI’s View of Agile

“There is no single best way to

define an ideal project life cycle.” –

PMBOK, p. 20

“The project manager, in

collaboration with the project

team, is always responsible for

determining what processes are

appropriate, and the appropriate

degree of rigor for each process, for

any given project.” – PMBOK, p. 37

www.pmi.org


PMBOK Project Management Process Groups

(mapped to)

Agile Project ManagementFramework

Initiating Envisioning

Planning Speculation

Executing Exploring

Controlling Adapting

Closing Closing

www.stickminds.com

Jim HighsmithErin Beierwaltes | agileaction.blogspot.com

www.dsdm.org

Plan Driven

Value Driven

Fixed Requirements Resources Time

Estimated Resources Time Features

Triple Constraints


XP (12)

•Pair Programming

•Planning Game

•Test-driven Development

•Whole Team

•Continuous Integration

•Refactoring

•Small Releases

•Coding Standards

•Collective Code

Ownership

•Simple Design

•System Metaphor

•Sustainable Pace

Scrum (9)

•Product Owner

•ScrumMaster

•Cross-functional Team

•Daily Scrum

•Sprint Planning

•Sprint Demo &

Retrospective

•Prioritized Backlog

•Time-boxed Sprints

•Potentially Shippable

each Sprint

Kanban (3)

•Visualized workflow

•Prioritized Tasks

•Limited WIP (Work in

Progress)

Agile Methods


Scrum Framework

Product Backlog

Sprint Backlog

2-4 weeks

Daily Scrum

Potentially Shippable


Scrum Framework

•Product owner•ScrumMaster•Team

Roles

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

Ceremonies

•Product backlog•Sprint backlog•Burndown charts

Artifacts

www.mountaingoatsoftware.com Erin Beierwaltes | agileaction.blogspot.com

The Sprint (Timeboxing)

2 to 4 weeks

Time boxed

Product Owner does NOT make changes mid sprint

Team can request changes to the sprint based on burndown progress


Scrum Framework


Roles


Ceremonies


Artifacts


Product Owner

Defines the features of the products

Decides on the release date and content

Prioritizes features

Accepts or rejects work results


ScrumMaster

Responsible for Scrum values and practices

Removes impediments

Shields the team from external interferences

Facilitates team decisions


Team

5-9 people (typically)

Larger projects expand with multiple scrum teams (scrum of scrums)

Cross-functional (developers, testers, documentation, ect)

Full time membership

Self organized

Membership only changes between sprints


Scrum Framework


Roles


Ceremonies


Artifacts


www.adyax.com

Daily Scrum

Meeting

Sprint Planning

Sprint Review and

Retrospective

Scrum Ceremonies


Scrum Framework


Roles


Ceremonies


Artifacts


Product Backlog

User Stories

As a ____, I want ____, so that ____.

Prioritized list of ALL desired work

Owned and kept up to date by Product Owner

Used during sprint planning

Reviewed Reprioritized before the start of every sprint

Sized with Story Points (by the team)


Sprint Backlog

List of TASKS that make up the required work for each Backlog item in the CURRENT sprint

Created and estimated by the TEAM

Updated by the TEAM

Data for the burndown chart


Product Backlog

www.inspectandadapt.com


Release Burndown

Based on average velocity

What happened

here?

Velocity = number of story points COMPLETED during the sprintErin Beierwaltes | agileaction.blogspot.com

Burndown Chart

What happened

here?


Waterfall vs. Scrum

Waterfall

Requirements

Predictive

Individuals

Sequential

Cost of change

Agile/Scrum

User Stories

Empirical

Teams

Iterative

Encouraged Change

Philipjeffs.comErin Beierwaltes | agileaction.blogspot.com

Transitioning to ScrumWaterfall to AgileE

rin

Be

ierw

alt

es

| a

gil

ea

ctio

n.b

log

spo

t.co

m

Waterfall vs. ScrumEvery framework has its place

Agile Project Management with Scrum by Ken Schwaber


Acceptance of ChangeKnow where You are

Know where They are

www.thecouldview.com


Agile CoachingFind or Become an Agile Coach


Learn More

http://www.scrumalliance.org/

http://www.mountaingoatsoftware.com/

http://www.coachingagileteams.com/

http://www.infoq.com/minibooks/scrum-xp-from-the-trenches (free downloadable book)

http://www.rallydev.com/agileblog/









http://www.infoq.com/minibooks/scrum-xp-from-the-trenches









