Girl Geeks Dinner - Scrum 101

Carolyn Sanders - Fronde Scrum 101 – end to end, minus the hype

Today – Scrum end to end

A tiny bit about where it came from

A bunch about how Scrum works…

… with examples from an actual project

Where to go for more information

Nothing at all about why it’s the best silver bullet since sliced bread

All of these things:

A set of engineering best practices that allow for rapid delivery of high quality software

A project process that encourages frequent inspection and adaptation

A philosophy that encourages team work and accountability

1. Agile Manifesto (philosophy)

We have come to value:

Individuals and interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan

That is, while there is value in the items on

the right, we value the items on the left more .

Agile Values (philosophy)

Openness: the project is for the stakeholders

Honesty: in estimating and planning

Courage: to face the consequences

Trust: in those individuals and their estimates

Money: because projects aren’t free

Commitment: to deliver on our promises

Agile Landscape Agile Manifesto and Values Agile Project Management (process) Agile Delivery (process) Agile Programming (engineering practices) Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited

Agile Delivery

Agile Delivery is:

small, self-managing, cross-functional teams,

delivering value frequently and incrementally

to the customers, by collaborating with them

Flavours:

Scrum

DSDM

Crystal

RUP

Agile Delivery Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited Traditional Project Agile Project Iterations – Design/Develop/Test First chance to see Last chance to change First chance to see Last chance to change Idea Business Case Reqts Design and Develop Test Train Deploy Idea Bus. Case HLR / Design / Setup 1 2 3 4 5 6 Deploy

Where Scrum started and who started it

1986: Hirotaka Takeuchi and Ikujiro Nonaka use the “rugby scrum” metaphor for product development

1991: Dr Jeff Sutherland (Easel) and Ken Schwaber (ADM), on real projects and calling it “Scrum”

And: Gabrielle Benefield and Pete Deemer at Yahoo

And: Alistair Cockburn, and Mike Cohn

3. The example project

Project H: building an Intranet in MOSS

For a client, with their experts

Three MOSS experts, a tester and a BA

Very constrained budget and deadline

Willing to trade off scope to get quality

“ Individuals and Interactions” – Scrum Roles Product Owner: get all the stakeholders’ input, prioritise the outputs Team: build the output. Self Organising, Cross Functional Scrum Master: get the process going well Stakeholders: have their say and do their bit Project Manager: not specified in Scrum Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited

“ Customer Collaboration” - the Product Backlog - the theory

All the stuff we could do:

Features

User Stories

Known Bugs

Explorations

The Vision

The Product Backlog

Specific items

Prioritised

Business value assigned

Effort estimated by team

The Product Backlog – estimation with Planning Poker The Fibonacci series: 1, 1, 2, 3, 5, 8, 13, 21, 34, 55… Planning Poker cards: 0, ½, 1, 2, 3, 5, 8, 13, 29, 40, 100, ?, ∞, coffee/pie James Grenning & Mike Cohn Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited

Sprint Planning – the theory Product Backlog items prioritised estimated How many hours the team can work in this Sprint, times “focus factor”*

Sprint Planning

- Break down the Backlog items into tasks

Agree on tasks

Estimate tasks

Commit to the outputs

Sprint Backlog

Estimated

Committed to

Sequenced

Sprint Planning – “Working Software” means what, exactly? Defining “Done” – hanselminutes.com Podcast 119 Quality (of the product) Support Documentation Content Testing Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited

“ Responding to Change” in the Daily Scrum – the theory

What I did yesterday

What I plan to do today

What’s holding me up

Rules Same time every day for 15 minutes No discussions during the Scrum Update the Sprint Backlog: hours’ effort remaining Update the Burndown © Pete Deemer and Gabrielle Benefield, The Scrum Primer Commercial in confidence | Copyright © 2008 Fronde Systems Group Limited

“ Responding to Change”: Sprint Review / Demo – theory and practice