Death By Scrum Meeting 2009

Death by Scrum

Pete Behrens
Agile Organization & Process Coach
© 2009 Trail Ridge Consulting, LLC pete@trailridgeconsulting.com 303.819.1809

Pete Behrens

Agile Organization & Process Coach

 Guide enterprise organizations in transitioning to an agile
organization implementing agile methods
 Services for agile assessment, alignment, training and coaching

Previous Experience
 Led development of the requirements management solution
RequisitePro – a core product in the IBM Rational product line – using
the Rational Unified Process (RUP)
 Consulted with EDS leading development of large data warehouse
solutions using Rapid Application Development (RAD)
© 2009 Trail Ridge Consulting, LLC 2

Certified Scrum
Coach (CSC) Program
 Guide-Level Certification equal to CST
 Initiated in 2007
 20 Certified Coaches Today (4 Local)
 Pete Behrens, Bob Hartman,
Richard Lawrence, Brad Swanson
 CSC Principles
1. Advise and Consult Agile Organizations
2. Facilitate Learning and Adoption
3. Mentor Agile Leadership at all levels
4. Guide Agile Organizational Development

 CSM Certification Testing
 CSM 2 Year Renewal
 CSPO Standardization

 Scrum Guide
 Member Only Content
 PMI and other partnerships

 User Groups Starting Worldwide
 Sao Paulo, Brazil - May 12-13
 Munich, Germany - October 19-21

What are you here?

WHAT SCRUM
CHALLENGES
ARE YOU FACING?


Do these sound familiar?
 “All members of the Scrum team should help testing.”
 “PM should recognize the value of quality over features.”

 “I’m pissed off to fix other guy’s bad design.”
 “A lot of shitty code.”

 “Sprints: I just hate the artificial time limits.”
 “Give us more time per Sprint.”

 “Scrum does not work unless management is committed
to not disrupting the team in the Sprint.”
 “Micro management causes a lack of motivation.”

We implement Scrum

“All team members are working in the sprint.

Developers are developing the backlog items.

Testers are testing the backlog items the
developers completed in the last sprint or two.

Product Management is preparing the items for
the next few sprints.”


How effective are meetings?


Scrum Skeleton?


Scrum Skeleton


What do you know about
Scrum?


Scrum?

Shu Ha Ri


Scrum?

Shu Ha Ri
Imitation Understanding Mastery


So what?

Most Organizations
IMPLEMENT Scrum

But don’t
UNDERSTAND Scrum

...and they are DYING

Scrum...

WHY WAS SCRUM
CREATED?


Why was Scrum Created?

TEAMS solve problems
better than individuals

Teams solve problems
better incrementally in
short TIMEBOXES

Why was Scrum Created?

TEAM

© 2009 Trail Ridge Consulting, LLC
TIMEBOX 15

The Haka


Teams...

HOW DO A GROUP
OF PEOPLE
BECOME A TEAM?


Creating a Team...

Need to move people from

DOING

OWNING

ScrumMaster = Coach


Release Planning = Clear Goal


Sprints = Practice


Field = Transparency


Meetings = The Team Entry


How long are your sprint
planning meetings?


planning meetings?
16
Sprint Planning (in hours)

12

8

4

0
1 2 3 4
Sprint Length (in weeks)

planning meetings?
16
Sprint Planning (in hours)

12

8 Why?
4

0
1 2 3 4

Adding all Scrum meetings...

16
Sprint Meetings (in hours)

c rum
y S e
12 Dail ctiv
o spe
etr
n tR
Spri w
8 vie
int Re
Spr
ann ing
Spri nt Pl
4

0
1 2 3 4

Adding all Scrum meetings...

16
Sprint Meetings (in hours)

c rum
y S e
12 Dail ctiv
pe

How much is o s
etr
n tR
Spri w
8 vie
int Re
Spr

4
too much? Spri nt Pl
ann ing

0
1 2 3 4

What else causes Meeting
“Death”?


Death by Meeting

 Meetings are
boring

 Meetings are
ineffective


Meetings are Boring - they lack
Action, Drama & Conflict


Meetings are Ineffective - they
lack context or focus
Meeting Type Time Required Purpose & Format Keys to Success

Daily 5 minutes Share daily schedules  Don’t sit down
and activities  Keep it administrative
Check-in
 Don’t cancel even when
some people can’t be there

Weekly 45 – 90 minutes Review weekly  Don’t set agenda until after
activities and metrics, initial reporting
Tactical and resolve tactical  Postpone strategic
obstacles and issues discussions

Quarterly 1 - 2 days Discuss, analyze,  Limit to one or two topics
brainstorm, and decide  Prepare and do research
Strategic upon critical issues  Engage in good conflict
affecting long-term  Get out of the office
success

Source: Death by Meeting, Patrick Lencioni

Death by Meeting - circa Scrum

Meeting Type Time Required Purpose & Format Keys to Success

Daily 5 minutes Share daily schedules  Don’t sit down

Daily Scrum
and activities  Keep it administrative
Check-in
 Don’t cancel even when
some people can’t be there

Weekly 45 – 90 minutes Review weekly  Don’t set agenda until after

Sprint Meetings
activities and metrics, initial reporting
Tactical and resolve tactical  Postpone strategic
obstacles and issues discussions

Quarterly 1 - 2 days Discuss, analyze,  Limit to one or two topics

Release Planning
brainstorm, and decide  Prepare and do research
Strategic upon critical issues  Engage in good conflict
affecting long-term  Get out of the office
success


Scrum Meeting Keys

Focus Timebox

Visualize Engage the Team


Scrum Meeting Keys

Focus Timebox

Strategic Tactical



Focus

Release Sprint
Planning Planning

Sprint
Review

Daily
Scrum
Sprint
Retro

Focus

Strategic Tactical Daily

Release Sprint
Planning Planning

Sprint
Review

Daily
Scrum
Sprint
Retro

Focus

Release Sprint Scrum

Release Sprint
Planning Planning

Sprint
Review

Daily
Scrum
Sprint
Retro

Do you play Planning Poker?


Do you play Planning Poker?

Why?

When?

Planning Poker is a Release
Tool

Release Sprint
Planning Planning

Sprint
Review

Daily
Scrum
Sprint
Retro

Tool


Release Sprint
Planning Planning

Sprint
Review

Daily
Scrum
Sprint
Retro

Tool

Release Sprint Scrum

Release Sprint
Planning Planning

Sprint
Review

Daily
Scrum
Sprint
Retro

Story Points are for looking ahead

Backlog Item Points Release
1. Login portal
2. Display minutes
5
3 Plan
3. Support ticket call 8
4. Remote login help 13
5. Update profile 2
6. Buy more time 8
7. Single sign-on 20
8. Log rotation 5
9. Timer display 3
10. Automatic logout 1
11. Usage warning 2
12. Exchange 12 integration 13
13. HP Openview API 20
14. XML API 8
15. 300 logins/min 13
16. Location tracking 5
17. Intrusion detection 13
18. Update MySQL DB 20
19. Update Web Stack 13
20. Update Linux Kernel 8
21. Support Novel Auth 13
22. Support RADIUS Auth 8
23. Scan & Block Int. 40
24. AP Manager Int. 20


Using Velocity Projections
160 160 Completed
Remaining
Remaining

120 120
Points

Points
80 80

40 40

0 0
Jan Feb Mar Apr May Jun Jul Aug Sep Jan Feb Mar Apr May Jun Jul Aug Sep

150.0 Completed 150.0 Completed
Remaining Remaining

112.5 112.5
Points

Points
75.0 75.0

37.5 37.5

0 0
Jan Feb Mar Apr May Jun Jul Aug Sep Jan Feb Mar Apr May Jun Jul Aug Sep


Scrum Meeting Keys

Focus Timebox



Scrum Meeting Keys

Focus Timebox

Strategic Tactical



Timebox

WHY DO WE
TIMEBOX?


Timeboxes drive focus, intensity,
decisions, productivity...

Waterfall

Intensity Scrum

Time


Timeboxes drive predictability

Predictable Uncertain Unpredictable

Sprint Sprint Sprint Sprint Sprint Sprint Sprint Sprint

Project Timeline


Daily Scrum Timebox

15 Minutes!


Timebox All Meetings?

Timeframe Daily Bi-weekly Quarterly

Daily Sprint Sprint Sprint Release
Scrum Retro Review Planning Planning

Minutes 5 - 15





Minutes 5 - 15 15 - 30 30 - 60 60 - 120 120 - 240





Minutes 5 - 15 15 - 30 30 - 60 60 - 120 120 - 240

1/2 Day


Timebox All Meetings!

Timeframe Daily

Daily
How do we
Sprint
Bi-weekly

Sprint Sprint
Quarterly

Release

Minutes
Scrum

5 - 15
do this
Retro

15 - 30
Review

30 - 60
Planning

60 - 120
Planning

120 - 240

effectively? 1/2 Day


Scrum Meeting Keys

Focus Timebox



Scrum Meeting Keys

Focus Timebox

Strategic Tactical



Visualize

Color Size

Time


Visualize Themes by Color


Visualize Types by Color


Visualize Role by Color


Visualize Size


Visualize Time


Scrum Meeting Keys

Focus Timebox



Scrum Meeting Keys

Focus Timebox

Strategic Tactical



Does this look familiar?


Engage the Team?


Scrum teams work together
and share commitment
Analysis Handoffs Traditional Phased-based
Lack Delays approach spreads the
of Ownership Design
team out over time
Task
Switching
Development
Lack
of Commitment Test
Compromised
Quality Deployment
Scrum brings the whole team
into short time-boxes Analysis
Shared Commitment
Shared Ownership Design
Shared Focus
More Productive Development
Quality Built In
Test

Deployment

Scrum Teams communicate

Face-to-face
Communication Effectiveness

At whiteboard
Face-to-face
Conversation
Video
Conversation
Phone Modeling
Videotape Conversation Options
Email
Conversation

Audiotape
Documentation
Paper
Options

Cold Hot

Engage the Team


Scrum teams work together


Scrum team share space


5 Min Review

Focus Timebox



5 Min Review

Focus Timebox

Strategic Tactical



Revisiting Planning Poker


Is there a better way to
engage the team?


Case Study: Salesforce.com


Where does team direction
come from?
CIO, CTO,
VP Engineering

Product Line Product Line Product Line
Manager Manager Manager

Functional Functional Functional Usability
Manager Manager Manager Engineering

DBA

PMO

Infrastructure

Scrum Quality
Team Assurance


Salesforce.com Releases

Last Waterfall Release

Since March 2007 every
agile release has been
deployed on-time
(down to the exact minute)


Salesforce.com 2006 vs. 2007


Salesforce.com Feedback

 89% are having the best time or good time
 38% increase in feature request delivered per
developer
 94% feature request increase from 2006 -
2007
 Since implementing our iterative development methodology which enables
us to deliver more frequent releases, we have seen statistically significant
improvements in our satisfactions scores across our service attributes from
our features to our platform.
 Wendy Close, Salesforce Customer Satisfaction Survey, Sr. Manager
Product Marketing, Salesforce.com


5 Min Session Retrospective

What will you take away? What did you miss?

 
 
 
 
 


Death By Scrum Meeting 2009

Recommended

Recommended

More Related Content

What's hot

What's hot (15)

Similar to Death By Scrum Meeting 2009

Similar to Death By Scrum Meeting 2009 (20)

More from Pete Behrens

More from Pete Behrens (10)

Recently uploaded

Recently uploaded (20)

Death By Scrum Meeting 2009