Certified Scrum Master Notebook November 5, 2013

1

Overview Scrum

2

Scrum Framework What is it…

Scrum is an agile framework that allows us to focus on delivering the highest business value in the shortest time;

It allows us to rapidly and repeatedly inspect actual working software every two to four weeks (Sprints);

The business sets the priorities. Teams self-organize to determine the best way to deliver the highest priority features.

In every sprint, anyone can see real working software and decide to release it as is or continue to enhance it for another sprint.

3

Overview Scrum Framework

4

Overview Scrum Process

5

Overview Scrum Values

6

Agile Manifesto

7

Processes & Tools Over * Individuals & interactions

Comprehensive documentation Over * Working software

Contract negotiation Over * Customer collaboration

Following a plan Over * Responding to change

*While there is value in the items on the right, we value the items on the left more.

Kent Beck, Mike Beedle, Arie van Bennekum , Alistair Cockburn, Ward Cunningham Martin Fowler, James Grenning, Jim Highsmith, Andrew Hunt, Ron Jeffries, Jon Kern, Brian Marick, Robert C. Martin, Steve Mellor, Ken Schwaber, Jeff Sutherl, and Dave Thomas

Agile Methodologies

Scrum

•Ken Schwaber, Jeff Sutherland

Extreme Programming (XP)

•Kent Beck, Ward Cunningham, Ron Jeffries

Crystal

•Alistair Cockburn

Lean Software Development

•Mary Poppendieck

Dynamic System Development Method (DSDM)

•Dane Faulkner

Adaptive Software Development (ASD)

•Jim Highsmith

Feature Driven Development (FDD)

•Jeff DeLuca

8

Agile Principles

Iterative and Incremental

Inspect and Adapt

9

Agile vs. Waterfall

Time

Waterfall

Sto

ries

Rem

ain

ing

Sp

rin

t 1

Sp

rin

t 3

Sp

rin

t 2

Sp

rin

t 4

Sp

rin

t 6

Rel

ease

1

7

8

9

Rel

ease

2

11

12

13

14

R4

Scrum

Delivers value only at the end

Delivers value at every release

Delivers value at every release

Delivers value at every release

Delivers value continuously

Analysis Design Develop Test Deploy

10

Agile vs. Waterfall

11

Analyze

Design

Develop

Test

Deploy

Agile Waterfall

Roles Product Owner

★ Works on and communicates a shared Vision for the product with the Team and other stakeholders

★ Gathers requirements (generally with assistance from others inside and outside the Scrum Team)

★ Manages and orders the Product Backlog

★ Accepts the software at the end of each Sprint

★ Manages the Release Plan

★ Manages Stakeholders

★ Manages the profitability of the product (ROI)

12

Roles Scrum Master

13

★ Helps the Team Members as facilitator, coach and servant leader to improve continuously

★ Works with the Product Owner to perform this role

★ Removes impediments to the Team Members

★ Keeps the process moving at all times

★ Ensures stakeholders are integrated

★ Socialises Scrum to the greater organisation

Roles Team

14

★ Estimates Product Backlog items (generally User Stories)

★ Contracts with the Product Owner to produce increments of deployable software...

★ ...and delivers them

★ Tracks own progress

★ Self-organises within the frame of their contract with the Product Owner and the organisation’s rules

Note: The collection of Team Members is termed the Development Team, Delivery Team or just team (with lower-case t). This is in contrast to the Scrum Team, which comprises one Product Owner, one Scrum Master and three to nine Team Members.

Artifacts Product Backlog

A prioritized list of functional and nonfunctional requirements and features to be developed with items of most business value and/or risk listed first.

The product backlog items of highest priority are granular enough to be readily understood by the Scrum Team and developed into an increment within a sprint.

Lower priority product backlog items are progressively less well-understood and granular.

This list transcends any one release and is constantly emerging and changing.

15

Artifacts Sprint Backlog

16

Artifacts Burndown Chart

17

Artifacts Burnup Chart

18

Ceremonies Time-Boxes

Release Planning

Sprint Planning

Sprint

The Daily Stand up

Sprint Review

Retrospective

19

Ceremonies Sprint Planning

A detailed list of all tasks needed in order to deliver the features chosen from the product backlog for the current Sprint.

It includes who owns the task, its status and estimated time to completion.

Individuals sign up for work Work is never assigned

Estimated work remaining is updated daily Estimated in hours

Work for the Sprint can emerge

20

Ceremonies Daily Answers

Haim Deutsch Copyright 2010

21

What did I Complete Yesterday

What will I complete Today

What is on my way

Ceremonies Sprint Review

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

22

Ceremonies Sprint Retrospective

Periodically take a look at what is and is not working

Output drives improvement actions plan and monitoring

Typically 60-120 minutes

Done after every sprint

Whole team participates Scrum Master

Team

Possibly Product owner, customers and others

23

Ceremonies Retrospective

Focus On

• Inquiring

• Dialogue

• Conversation

• Understanding

Focus Off

• Advocacy

• Debate

• Argument

• Defending

24

Ceremonies Retrospective

Structuring

Set the Stage – 5%

Gather Data – 20-30%

Generate Insight – 30-50%

Decide what to do 15-20%

Close the Retrospective 10%

Shuffle time 10-15%

Total – 100%

25

Ceremonies Retrospective

26