Scrum discussion

Roshan Venugopal

Certified Scrum Master

With Emdeon since 2008.

Passionate about Scrum, web2.0 and open source

[email protected]

6/20/20142

Name of the person on your left

His/her Project

His/her favorite Football team

What brings you here ?

6/20/20143

Beginnings

In-depth

Advanced Scrum

6/20/20144

6/20/20145

Most companies approach software development as follows:

dream up a project. set a date for launch hire a bunch of coders whip them until they’re half dead. hire some testers testers reports bugs PM blames testers for bugs while reporting ‘green’ Business has no idea what was accomplished Time passes quickly…Its already 2years Unfortunately the market has changed and we are out with the

project is technically obsolete

Start over.

Concept first discussed by H. Takeuchi

and I. Nonaka in their seminal HBR article

"The New New Product Development

Game“ (Jan 1986)

6/20/20146

Jeff Sutherland was frustrated by this cycle

and wanted to deploy new products fast

without the ‘death-march’ aspect. He

discovered Scrum in an HBR article and

first implemented it in 1993 at Easel Corp.

6/20/20147

Other iconoclasts banded together to form the Agile alliance to promote Agile/Scrum methodologies.• Scrum is the management framework for product

development promoted by the alliance.

Agile though based on empirical experiences borrows from Lean Manufacturing, Six sigma, Wideband Delphi etc.

6/20/20148

We 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

6/20/20149

6/20/201410

Agile

Scrum FDD

RADXP

Process to manage a self organizing team that uses agile principles to focus on delivering the greatest business value in the shortest time.• Code fast, Release often.

• Time boxing Releases.

• Collaboration with stakeholders.

• Management wrapper for agile engineering processes.

• Adapt to changing marketplace

6/20/201411

Value to customerCollaboration and feedbackMotivated teamsResponsibility and decision making at

lowest levelWork at sustainable paceFace to face communicationFrequent delivery of working software Inspect and AdaptNo surprises

6/20/201412

6/20/201413

6/20/201414

When you accept a challenge, see it through.

6/20/201415

6/20/201416

Water Fall

Iterative

Scrum

Requirements Code Testing Implementation

Analysis

&

Design

RequirementsCode,

Test

Prototype,

Analysis

Design

Implementation

Prototype,

Analysis

Design

Code,

Test

Some

RequirementsSprint Sprint Sprint Sprint

Google (Adwords. One of the biggest money making apps in Google’s history)• Government NASA, VA DMV, BBC, DoD

• Healthcare GE Healthcare

• Manufacturing HP, Siemens, Nokia

• Software Products Microsoft, Electronic Arts, High Moon Studios

• Finance Capital One, Intuit

Emdeon : Real Time Claiming and ePayment projects.

6/20/201417

6/20/201419

Sprint 1

Sprint 2

Sprint 4

Sprint 3

Product Backlog

Sprint Backlog

SprintApplication

Daily Scrum

Working

Increment

Sprint is a time boxed build increment (no changes accepted during a sprint)

Normally lasts for 2-4 weeks Input Sprint backlog built by the team containing

User Stories/Use Cases ordered by priority. Output Done User stories and Sprint demo to

Product Owner Each User story is rated based on importance,

complexity, Feature, time needed. Every Sprint must deliver atleast one finished

piece of functionality.

6/20/201420

3 actors

3 artifacts

3 ceremonies

6/20/201421

Cross functional team consisting 5-9 members

Organizes itself and its work

Preferable co-located or must have visual and

voice connection

Plans and creates sprint backlog

Attends daily scrum meeting

Completes all tasks required for a user story

Demos the sprint to Product owner

Chickens and Pigs

6/20/201422

Exercise

Divide into teams

Create a team name

6/20/201423

Plans and creates Product backlog

Decides on release date

Can change Priority and backlog at the

beginning of a sprint.

Attends scrum meetings as needed

Accept or Reject Sprint deliverables

Must have the vision and expertise

6/20/201424

6/20/201425

http://www.implementingscrum.com/2009/01/12/the-single-wringable-neck-scrum-style/

Organizes planning sessions for Product Owner

and Team

Ensures co-operation inside team across

functions and roles

Removes barriers and external interferences

Plans Daily scrum meetings and Sprint Demos

Product Owner engagement

Servant leader

6/20/201426

Conducted before the beginning of a sprint

Joint planning by team and Product Owner

Create prioritized backlog of user stories

and tasks for given sprint

Mutually define ‘done’ for the sprint

6/20/201427

Duration 1 month (20-22 working days)

Day 1 Sprint Planning

Day 2 – 14/15 Code/Test(fix)/Build

Day 15/16 – 18/19 Integration & Test

Day 20/21 Demo and Retrospective

6/20/201428

Typically, Sprints have a unique feature or

theme.

Helps focus the PO and Team to a united

goal

Helps manage backlogs

Helps in envisioning the product roadmap

Examples ?

6/20/201429

Daily 15 min meetingOnly 3 questions to be asked and answered

• What have you done in last 24 hours ?

• What do you plan to do next 24 hours ?

• Any Obstacles ?

Is not a status update to Scrum master or Product owner

Team will assign task themselvesOnly pigs will talk, chickens will listenTeam will co-ordinate the meetingScrum Master to resolve obstacles

6/20/201430

6/20/201431

Team demos the Sprint deliverables to

Product owner

Product Owner can accept or reject the

deliverables

Q & A session with team

Demo is actual product demonstration and

not a ppt deck.

6/20/201432

Q & A session with team

What went wrong

What was done right

Improvements for next sprint

Celebrate sprint success

6/20/201433

As a <type of user> I want to <action > so that <Business Value>

AttributesSize – Use Cases per storyComplexity – H/M/LTime needed – story pointsPriority – Must have/ Good to have

Based on the above, Rank each User story in the Backlog

6/20/201434

Exercise

Each team to create 3-4 Business goals to

develop an portal for your football team.

Discuss

6/20/201435

Product Owner to co-ordinate

Decompose epics to right sized-stories

Prioritize at a theme level• Kano analysis

• Relative weights

• Net Present Value

6/20/201436

Calculate the number of days to build a wall

Est. effort req. is 160 man hours

Exercise:

Size the team and estimate the duration.

6/20/201437

http://en.wikipedia.org/wiki/The_Mythical_Man-Month

Member Portal for Medical Insurance BenefitsAs a user I need to view my available benefitsAs a user I need to view my claimsAs a user I need to call help desk to reset my

passwordAs a helpdesk analyst I need to edit user

profileAs a Company representative I need to view

the website usage statistics

6/20/201438

Exercise

Create 10 user stories based on Business

goals• Prioritize

• Size using Fibonacci scale 1,2,3,5,8,13

• Each user story must be linked to a business goal

• Rank the user stories

• Assume 2 story points per man day

Discuss

6/20/201439

Member Portal for Medical Insurance BenefitsAs a user I need to view my available benefits

• Create a screen for user to register- 8hrs

• Create security features for users when logging- 15 hrs

• Get data feed from eligibility d/b- 2hrs

• Write Ajax code to display member benefits- 12 hrs

• Test screen registration- 1 hr

• Test member benefits display -3 hr

• Test website security -9 hr

6/20/201440

6/20/201441

Preferably displayed in the Scrum roomMust contain all the User stories in the Sprint

backlogMust contain 3 columns / rows to denote user

stories that have• Not been started

• Work In Progress Includes coding complete but testing in progress

• Been completed Must include only items that has been ‘done’ and no more

work is needed.

6/20/201442

6/20/201443

To do WIP Done

Task1

Task2

Task3

Task4

Task5

Task6

Task7

Task8

Task9

Sprint 8 is in progress. 6 days left for Demo. Comment on the

taskboard.

6/20/201444

0

100

200

300

400

500

600

700

800

900

1000

10

/17

/200

8

10

/18

/200

8

10

/19

/200

8

10

/20

/200

8

10

/21

/200

8

10

/22

/200

8

10

/23

/200

8

10

/24

/200

8

10

/25

/200

8

10

/26

/200

8

10

/27

/200

8

10

/28

/200

8

10

/29

/200

8

10

/30

/200

8

10

/31

/200

8

11

/1/2

008

11

/2/2

008

11

/3/2

008

11

/4/2

008

11

/5/2

008

11

/6/2

008

11

/7/2

008

11

/8/2

008

11

/9/2

008

11

/10

/200

8

11

/11

/200

8

11

/12

/200

8

11

/13

/200

8

11

/14

/200

8

11

/15

/200

8

11

/16

/200

8

11

/17

/200

8

Ho

urs

Left

Sprint Burndown Chart

Rate at which story points were completed

per sprint by a team.

Very useful in estimation and planning for

subsequent sprints.

Used to track effectiveness of Scrum as

velocity increases every sprint.

6/20/201445

Typically Scrum assumes 5-5.5 hours of

productive work every working day.

Vacations and holidays are included in

planning.

Team decides the available capacity.

Additional specialized capacity has to be

accounted for like DBAs etc.

6/20/201446

Typically, Sprints have a unique feature or

theme.

Helps focus the PO and Team to a united

goal

Helps manage backlogs

Helps in envisioning the product roadmap

Examples ?

6/20/201447

Exercise

Organize your User stories and tasks into

a Sprint backlog

Discuss

6/20/201448

6/20/2014 49

XP –eXtreme Programming

Scrum is the management wrapper for XP

XP has a set of rules for engineering

including• Pair Programming

• Test Driven Development

• Automated unit Tests

• Code Refactoring

6/20/201450

Agile culture & PMO

Competition

Management Responsibilities

Documentation and Signoffs

Finger pointing

Trust and Openness

6/20/201451

Planning• - Don’t plan too ahead. Goals are reached one

step at a time.

• Involve team in planning

Testing in Scrum• Testing Automation

• Work should be interesting for testers

• TDD – Testing as development activity

6/20/201452

Development Environment• Automated unit tests

Common sense items• Code Review

• Help documentation

• Performance testing

• Defect tracking

Implementation Environment• Automated builds

6/20/201453

6/20/201454

Its defined as the buildup of small issues

or malfunctions in the code base which

needs corrective action.

Fixing(repaying) this will have not business

benefit but needs to be done else over

time debt gets escalated to unmanageable

levels.

6/20/201455

Nokia Test

Scrum Smells

Planning Poker

Refactoring

Scrum tools

6/20/201456

6/20/201457

6/20/201458

4 points from each team

Discuss

6/20/201459

Salesforce.com

Top down approach• Scrum mentor to coach CxOs

• Scrum Center of Excellence

• Coach Scrummasters and Product Owners

• Scrum mentor to assist teams

6/20/201460

Google.com

Bottom up approach• Influential developers implement Scrum

• Demonstrate Scrum efficiencies

• Attain critical mass by reaching out to

management

6/20/201461

Discuss

Product Backlog actual example

6/20/201462

Read articles/white papers/presentations

Implement scrum

Get Certified• Certified Scrum Master

• Certified Product Owner

6/20/201463

Packaged commonsense

Old wine in new bottle

Commercialized and watered down

Newest buzzword

Read ‘Agile Disease’ blog by Luke Halliwell

6/20/201464

Scrum xp from the trenches

ControlChaos

Mountain Goat Software

Rally software

Infoq.com (look for papers/presentations

on Scrum/Agile)

ScrumAlliance.org (look for

papers/articles/presentations on Scrum)

notesfromatooluser.com

6/20/201465