Andreas Hägglund

Introducing Scrum A Collaborative Game

11K

slideshare.net/andreashagglund

@ahab1972

andreashagglund

Thank you to our sponsor! 11K

https://www.youtube.com/watch?v=WxiuE-1ujCM

Scrum in 111 seconds

11K

Two big events in 1986... “The… ’relay race’ approach to product

development…may conflict with the goals of

maximum speed and flexibility. Instead a

holistic or ’rugby’ approach — where a team

tries to go the distance as a unit, passing the

ball back and forth—may better serve today’s

competitive requirements.”

Hirotaka Takeuchi and Ikujiro Nonaka, “The

New New Product Development Game”,

Harvard Business Review, January 1986.

11K

• Scrum is an agile process that allows us to focus on delivering

the highest business value in the shortest time using empirical

process control.

• It allows us to rapidly and repeatedly inspect actual working

software (every two weeks to one month).

• The business sets the priorities. Teams self-organize to

determine the best way to deliver the highest priority features.

• Every two weeks to a month anyone can see real working

software and decide to release it as is or continue to enhance

it for another sprint.

Scrum in 100 words

11K

History of Scrum ● Pre 1986 Lean & Agile Practices ● 1986 The New New Product Development Game published ● 1993 Jeff Sutherland - Easel Corp, Ken Schwaber – ADM ● 1995 OOPSLA Conference ● 1999 Scrum patterns in PLOPD4 published ● 2001 Agile Manifesto signed ● 2001 Agile Software Development with Scrum published ● 2002 Scrum Alliance founded ● 2004 Agile Project Management with Scrum published ● 2009 Scrum.org founded ● 2010 Scrum Guide published ● 2013 Scrum Guide translated to Arabic

11K

Who’s using it? ● Microsoft ● Yahoo ● Google ● Electronic Arts ● Lockheed Martin ● Philips ● Siemens ● Nokia ● Ericsson ● Intuit

● Boeing ● Spotify ● John Deere ● Sabre ● Salesforce.com ● Time Warner ● Turner Broadcasting ● BBC ● IBM ● Thomson Reuters

11K

Who’s not?

11K

What are they developing? ● Commercial software ● In-house development ● Contract development ● Fixed-price projects ● Financial applications ● ISO 9001-certified applications ● Embedded systems ● 24x7 systems with 99.999%

uptime requirements ● the Joint Strike Fighter

● Video game development ● FDA-approved, life-critical systems ● Satellite-control software ● Websites ● Handheld software ● Mobile phones ● Network switching applications ● ISV applications ● Some of the largest applications in

use

11K

Scrum Characteristics ● No specific engineering practices prescribed ● Requirements are captured as items in a list of “product

backlog” ● Self-organizing teams ● Product progresses in a series of month-long “sprints” ● Uses generative rules to create an agile environment for

delivering projects

● Empirical Process

11K

Why Self-Organizing?

11K

Why is a sprint just a month long?

Plan sprint durations around how long you can commit to

keeping change out of the sprint

11K

What is a generative rule?

Generative Rules ● A minimum set of things you must always do, to learn what

to do in any specific situation

● Helps you help yourself

Inclusive rules

● All the things you should do under all situations.

● Solves the problem for you

11K

What is an Empirical Process

Empirical Process ● Unpredictable ● Unrepeatable ● Requires scientific use

of data to understand

process

Defined Process

● Predictable ● Repeatable

● Completely understood ● Automatable

11K

Software Development Is Unrepeatable!

Complex

Anarchy

Technology

Requirem

ents

Far from

Agreement

Close to

Agreement

Clo

se to

Ce

rta

inty

Fa

r fr

om

Ce

rta

inty

Source: Strategic Management and

Organizational Dynamics by Ralph Stacey in

Agile Software Development with Scrum by

Ken Schwaber and Mike Beedle.

11K

Simple

Pillars of Empirical Process Control

● Visibility ● Inspection ● Adaptation

11K

The Agile Values

Process and tools Individuals and interactions over

Following a plan Responding to change over

Comprehensive documentation Working software over

Contract negotiation Customer collaboration over

11K

I terat ive

11K

Water fa l l Analysis

Design

Implementation

Test

Deployment

Icons designed by Freepik

Release 1 Release 2 Release 3

Release 1

Release 4 Release 5

Putting it all together – Scrum Framework

11K

Sprints ● Scrum projects make progress in a series of “sprints” ● Typical duration is 2–4 weeks or a calendar month at

most ● A constant duration leads to a better rhythm ● Product is designed, coded, and tested during the sprint

11K

Scrum Framework

•Product owner

•ScrumMaster

•Team

Roles

•Sprint planning

•Sprint review

•Sprint retrospective

•Daily scrum meeting

Ceremonies

•Product backlog

•Sprint backlog

•Burndown charts

Artifacts

11K

Artifacts

•Product owner

•ScrumMaster

•Team

Roles

•Sprint planning

•Sprint review

•Sprint retrospective

•Daily scrum meeting

Ceremonies

•Product backlog

•Sprint backlog

•Burndown charts

Artifacts

11K

Product Backlog ● The requirements ● A list of all desired work on the

project ● Ideally expressed such that

each item has value to the users

or customers of the product

● Prioritized by the product owner

● Reprioritized at the start of each

sprint This is the

product backlog

11K

Rough Sizing: T-shirts or Story points

XL

L

M

S

XS

11K

0, 0.5, 1, 2, 3,

5, 8, 13, 20,

40, 100, ?

A Sample Product Backlog Backlog item Size

Allow a guest to make a reservation 3

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

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

As a hotel employee, I can run RevPAR reports (revenue-

per-available-room) 8

Improve exception handling 8

... 30

... 50

11K

Managing the Sprint Backlog ● Individuals sign up for work of their own choosing ● Work is never assigned ● Estimated work remaining is updated daily

11K

Managing the Sprint Backlog ● Any team member can add, delete or change the sprint

backlog ● Work for the sprint emerges ● If work is unclear, define a sprint backlog item with a

larger amount of time and break it down later

● Update work remaining as more becomes known

11K

A Sample Sprint Backlog Tasks

Code the user interface

Code the middle tier

Test the middle tier

Write online help

Write the foo class

Mon

8

16

8

12

8

Tues

4

12

16

8

Wed Thur

4

11

8

4

Fri

8

8

Add error logging

8

10

16

8

8

11K

The Scrumboard

Todo Doing Done

Risk

Story

11K

Sample Task Template 11K

A Sprint Burndown Chart

Ho

urs

11K

More Metrics

The trend is your friend

Cumulative Flow Delivered Value Velocity

11K

Scrum Framework

•Product owner

•ScrumMaster

•Team

Roles

•Product backlog

•Sprint backlog

•Burndown charts

Artifacts

•Sprint planning

•Sprint review

•Sprint retrospective

•Daily scrum meeting

Ceremonies

11K

Sprint planning meeting

11K

How to find an agreed upon solution: https://www.youtube.com/watch?t=37&v=8Amu3UBj-qw

Sprint planning meeting

Sprint prioritization

• Analyze and evaluate product backlog

• Select sprint goal

Sprint planning

• Decide how to achieve sprint goal

(design)

• Create sprint backlog (tasks) from

product backlog items (user stories /

features)

• Estimate sprint backlog in hours

11K

Sprint planning meeting

Sprint prioritization

• Analyze and evaluate product backlog

• Select sprint goal

Sprint planning

• Decide how to achieve sprint goal

(design)

• Create sprint backlog (tasks) from

product backlog items (user stories /

features)

• Estimate sprint backlog in hours

Business

conditions

Team

capacity

Product

backlog

Technology

Current

product

11K

Sprint planning meeting

Sprint prioritization

• Analyze and evaluate product backlog

• Select sprint goal

Sprint planning

• Decide how to achieve sprint goal

(design)

• Create sprint backlog (tasks) from

product backlog items (user stories /

features)

• Estimate sprint backlog in hours

Sprint

goal

Sprint

backlog

Business

conditions

Team

capacity

Product

backlog

Technology

Current

product

11K

The Sprint Goal A short statement of what the work will be focused on during the sprint

Database Application

Financial services

Life Sciences

Support features necessary for population

genetics studies.

Support more technical indicators than

company ABC with real-time, streaming data.

Make the application run on SQL Server in

addition to Oracle.

11K

Sprint Planning ● Team selects items from the product backlog they can commit to

completing ● Sprint backlog is created ● Tasks are identified and each is estimated (1-16 hours) ● Collaboratively, not done alone by the ScrumMaster

● High-level design is considered

11K

As a vacation planner, I want to see photos of the hotels so that I will get

a feeling for them.

Code the middle tier (8 hr)

Code UI (8 hr)

Write tests (4 hr)

Meet PO (2 hr) Code Foo-class (6 hr)

Update performance tests

(4 hr)

The Daily Scrum Parameters

● Daily ● 15 Minutes ● Stand Up

Not for problem solving ● Whole world is invited

● Only team members, ScrumMaster, product owner, can talk

Helps avoid unnecessary meetings

11K

3 Questions for everyone

These are not status for the ScrumMaster. They are

commitments in front of peers

What did you do yesterday? 1

What will you do today? 2

Is anything in your way? 3

11K

The 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) ● Whole team participates

● Invite the world

A Review:

https://www.youtube.com/watch?v=Q6jMgmPIxmk

11K

The Sprint Retrospective ● Periodically take a look at what is and is not working ● Typically 15–30 minutes ● Done after every sprint

● Whole team participates (ScrumMaster, Product owner,

Team, Possibly customers and others)

11K

Example Retrospective Gather the whole team and discuss what you should:

● Stop doing ● Continue doing ● Start doing

11K

Scrum Framework

•Sprint planning

•Sprint review

•Sprint retrospective

•Daily scrum meeting

Ceremonies

•Product backlog

•Sprint backlog

•Burndown charts

Artifacts

•Product owner

•ScrumMaster

•Team

Roles

11K

Product Owner ● Define the features of the product ● Decide on release date and content ● Be responsible for the profitability of the product (ROI) ● Prioritize features according to market value

● Adjust features and priority every iteration, as needed

● Accept or reject work results

11K

Product Owner Videos

● Why it’s important to have a committed product owner:

https://www.youtube.com/watch?v=BTTdHW8Z668 ● How to negotiate as a product owner:

https://www.youtube.com/watch?v=ZG-NgkHv52Y ● Product ownership in a nutshell:

https://www.youtube.com/watch?v=502ILHjX9EE

11K

ScrumMaster ● Communicates with management ● Responsible for enacting Scrum values and practices ● Removes impediments ● Ensure that the team is fully functional and productive

● Enable close cooperation across all roles and functions

● Shield the team from external interferences

The ScrumMaster:

https://www.youtube.com/watch?v=oheekef7oJk

11K

The Team ● Typically 5-9 people ● Cross-functional ● Members should be full-time ● May be exceptions (e.g., database administrator)

11K

The Team ● Self-organizing (No titles!) ● Membership should change only

between sprints

11K

Scalability ● Typical individual team is 7 ± 2 people ● Scalability comes from teams of teams

● Factors in scaling ● Type of application

● Team size

● Team dispersion

● Project duration

11K

Scaling ● Scrum of Scrums

● Nexus – Scrum.org ● LeSS - http://less.works/ ● SAFe -

http://www.scaledagileframe

work.com/

Why synchronized sprint length

is important:

https://www.youtube.com/watch

?t=12&v=Suugn-p5C1M

11K

Scaling through Scrum of Scrums

11K

Scrum of Scrum of Scrums

11K

Where to go next ● www.agilemiddleeast.org

● stateofagile.com

● www.scrumguides.org

● www.scrumalliance.org

● www.scrum.org ● www.agilealliance.org

● www.enterprisescrum.com

● www.mountaingoatsoftware.com/scrum

11K

A Reading List ● Agile and Iterative Development: A Manager’s Guide by Craig

Larman ● Agile Estimating and Planning by Mike Cohn ● Agile Project Management with Scrum by Ken Schwaber

● Agile Retrospectives by Esther Derby and Diana Larsen

● Agile Product Management with Scrum by Roman Pichler

● User Story Mapping by Jeff Patton

● Scrum and XP from the trenches by Henrik Kniberg

11K

A Reading List ● Agile Software Development Ecosystems by Jim Highsmith ● Agile Software Development with Scrum by Ken Schwaber and

Mike Beedle ● Scrum and The Enterprise by Ken Schwaber

● Succeeding with Agile by Mike Cohn

● User Stories Applied for Agile Software Development by Mike Cohn

● Software in 30 days by Ken Schwaber & Jeff Sutherland

● Enterprise Scrum by Mike Beedle

● Agile Testing by Lisa Crispin

11K

Credit

This presentation is based on Mike Cohn’s reusable Scrum

presentation.

mike@mountaingoatsoftware.com

www.mountaingoatsoftware.com

https://www.mountaingoatsoftware.com/agile/scrum/a-reusable-scrum-

presentation

(720) 890-6110 (office)

11K

Lean & Agile Middle East

info@meagile.com

https://agilemiddleeast.org/ Contact

Information

https://www.facebook.com/AgileMiddleEast

https://twitter.com/MEAgile

https://www.linkedin.com/groups?home=&gid=8133203

11K

Lean & Agile Middle East

Upcoming

Events

Professional Scrum Master 22-23 July, Dubai

Call for papers: Agile ME Summit, Sept 30

Procurement and Agile PM, 4-5 Oct., Dubai

Introducing Lean & Agile, Abu Dhabi, Oct.

Introducing Lean & Agile, Dubai, Oct.

Agile ME Summit 2016, March 19, Dubai

11K

Andreas Hägglund

Learning is optional,

so is survival

I run projects and make organizations more efficient

by working as:

● Change Agent

● Trainer & Coach

● Project Manager/Scrum Master

● Product Owner/Business Developer

17 years of experience of Management & IT

11K

Andreas Hägglund

Contact

Information

slideshare.net/andreashagglund

www.kravanalys.se/category/inenglish www.systemvaruhuset.se

@ahab1972

andreashagglund

11K

Q&A 11K