death by scrum meeting - laugh | grow | scrum · 3/16/2009 · death by meeting - circa scrum 8...
Post on 05-Apr-2020
5 Views
Preview:
TRANSCRIPT
© 2009 Trail Ridge Consulting, LLC
Pete BehrensAgile Organization & Process Coachpete@trailridgeconsulting.com 303.819.1809
Death by Scrum Meeting
© 2009 Trail Ridge Consulting, LLC 2
Pete Behrens
Agile Organization & Process Coach Certified Scrum Trainer Certified Scrum 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
How long are your sprint planning meetings?
3
0
4
8
12
16
1 2 3 4
Spr
int
Plan
ning
(in
hou
rs)
Sprint Length (in weeks)
© 2009 Trail Ridge Consulting, LLC
Adding all Scrum meetings...
4
0
4
8
12
16
1 2 3 4
Spri
nt M
eetin
gs (
in h
ours
)
Sprint Length (in weeks)
Sprint PlanningSprint ReviewSprint RetrospectiveDaily Scrum
© 2009 Trail Ridge Consulting, LLC
Death by Meeting
5
Meetings are boring
Meetings are ineffective
© 2009 Trail Ridge Consulting, LLC
Meetings are Boring - they lack Action, Drama & Conflict
6
© 2009 Trail Ridge Consulting, LLC
Meetings are Ineffective - they lack context or focus
7
Meeting Type Time Required Purpose & Format Keys to Success
DailyCheck-in
5 minutes Share daily schedules and activities
Don’t sit down Keep it administrative Don’t cancel even when
some people can’t be there
WeeklyTactical
45 – 90 minutes Review weekly activities and metrics, and resolve tactical obstacles and issues
Don’t set agenda until after initial reporting
Postpone strategic discussions
Quarterly Strategic
1 - 2 days Discuss, analyze, brainstorm, and decide upon critical issues affecting long-term success
Limit to one or two topics Prepare and do research Engage in good conflict Get out of the office
Source: Death by Meeting, Patrick Lencioni
© 2009 Trail Ridge Consulting, LLC
Death by Meeting - circa Scrum
8
Meeting Type Time Required Purpose & Format Keys to Success
DailyCheck-in
5 minutes Share daily schedules and activities
Don’t sit down Keep it administrative Don’t cancel even when
some people can’t be there
WeeklyTactical
45 – 90 minutes Review weekly activities and metrics, and resolve tactical obstacles and issues
Don’t set agenda until after initial reporting
Postpone strategic discussions
Quarterly Strategic
1 - 2 days Discuss, analyze, brainstorm, and decide upon critical issues affecting long-term success
Limit to one or two topics Prepare and do research Engage in good conflict Get out of the office
Daily ScrumSprint MeetingsRelease Planning
© 2009 Trail Ridge Consulting, LLC
Scrum Meeting Keys
9
① Focus ② Timebox
③ Visualize ④ Engage the Team
Strategic Tactical
© 2009 Trail Ridge Consulting, LLC
Focus
10
Strategic Tactical Daily
Release Sprint Scrum
Release Planning
Sprint Planning
Sprint Review
Sprint Retro
Daily Scrum
© 2009 Trail Ridge Consulting, LLC
Do you play Planning Poker?
11
© 2009 Trail Ridge Consulting, LLC
Planning Poker is a Release Tool
12
Strategic Tactical Daily
Release Sprint Scrum
Release Planning
Sprint Planning
Sprint Review
Sprint Retro
Daily Scrum
© 2009 Trail Ridge Consulting, LLC
Story Points are for looking ahead
Backlog Item Points 1. Login portal 52. Display minutes 33. Support ticket call 84. Remote login help 135. Update profile 26. Buy more time 87. Single sign-on 208. Log rotation 59. Timer display 310. Automatic logout 111. Usage warning 212. Exchange 12 integration 1313. HP Openview API 2014. XML API 815. 300 logins/min 1316. Location tracking 517. Intrusion detection 1318. Update MySQL DB 2019. Update Web Stack 1320. Update Linux Kernel 821. Support Novel Auth 1322. Support RADIUS Auth 823. Scan & Block Int. 4024. AP Manager Int. 20
ReleasePlan
13
© 2009 Trail Ridge Consulting, LLC
Using Velocity Projections
0
40
80
120
160
Jan Feb Mar Apr May Jun Jul Aug Sep
Points
Remaining
0
40
80
120
160
Jan Feb Mar Apr May Jun Jul Aug Sep
Points
RemainingCompleted
0
37.5
75.0
112.5
150.0
Jan Feb Mar Apr May Jun Jul Aug Sep
Points
RemainingCompleted
0
37.5
75.0
112.5
150.0
Jan Feb Mar Apr May Jun Jul Aug Sep
Points
RemainingCompleted
14
© 2009 Trail Ridge Consulting, LLC
Product & Process Focus
15
Strategic Tactical Daily
Release Sprint Scrum
Release Planning
Sprint Planning
Sprint Review
Sprint Retro
Daily Scrum
P
roce
ss
Prod
uct
© 2009 Trail Ridge Consulting, LLC
Product & Process Focus Issues
16
Sprint Reviews eroding into process questions about why we didn’t get things done and what to do about it
Sprint Planning sessions spending more time about how to plan or not plan vs. actually planning the product increment
Daily Scrums used to solve problems
© 2009 Trail Ridge Consulting, LLC
Scrum Meeting Keys
17
① Focus ② Timebox
③ Visualize ④ Engage the Team
Strategic Tactical
© 2009 Trail Ridge Consulting, LLC
Sprint Timebox
18
2 - 4 weeks!
© 2009 Trail Ridge Consulting, LLC 19
Timeboxes drive focus, intensity, decisions, productivity...
Time
Intensity
Waterfall
Scrum
© 2009 Trail Ridge Consulting, LLC
Timeboxes drive predictability
20
Predictable Uncertain Unpredictable
Project Timeline
Sprint Sprint Sprint Sprint Sprint Sprint Sprint Sprint
© 2009 Trail Ridge Consulting, LLC
Daily Scrum Timebox
21
15 Minutes!
© 2009 Trail Ridge Consulting, LLC
Timebox All Meetings?
22
Release Planning
Sprint Planning
Sprint Review
Sprint Retro
Daily Scrum
120 - 24060 - 12030 - 6015 - 305 - 15Minutes
Timeframe Daily Bi-weekly Quarterly
1/2 Day
© 2009 Trail Ridge Consulting, LLC
Scrum Meeting Keys
23
① Focus ② Timebox
③ Visualize ④ Engage the Team
Strategic Tactical
© 2009 Trail Ridge Consulting, LLC
Visualize
24
① Color ② Size
③ Time ④ Change
© 2009 Trail Ridge Consulting, LLC
Visualize Themes by Color
25
© 2009 Trail Ridge Consulting, LLC
Visualize Types by Color
26
© 2009 Trail Ridge Consulting, LLC
Visualize Role by Color
27
© 2009 Trail Ridge Consulting, LLC
Visualize Size
28
© 2009 Trail Ridge Consulting, LLC
Visualize Size
29
© 2009 Trail Ridge Consulting, LLC
Visualize Time
30
© 2009 Trail Ridge Consulting, LLC
Visualize Time
31
© 2009 Trail Ridge Consulting, LLC
Visualize Change
32
© 2009 Trail Ridge Consulting, LLC
Visualize Change
33
© 2009 Trail Ridge Consulting, LLC
Scrum Meeting Keys
34
① Focus ② Timebox
③ Visualize ④ Engage the Team
Strategic Tactical
© 2009 Trail Ridge Consulting, LLC
Engage the Team?
35
© 2009 Trail Ridge Consulting, LLC
Engage the Team?
36
© 2009 Trail Ridge Consulting, LLC
Engage the Team?
37
© 2009 Trail Ridge Consulting, LLC
Scrum teams work together - Engage the Team
Analysis
Design
Development
Test
Deployment
Analysis
Design
Development
Test
Deployment
Traditional Phased-based Approach
Scrum time-boxes the life-cycle
Handoffs
Delays
TaskSwitching
Lackof Ownership
Lackof Commitment
CompromisedQuality
Shared CommitmentShared OwnershipShared FocusMore ProductiveQuality Built In
38
© 2009 Trail Ridge Consulting, LLC 39
Scrum Teams communicate
Cold Hot
Com
mun
icat
ion
Effe
ctiv
enes
s
DocumentationOptions
ModelingOptionsVideotape
EmailConversation
Audiotape
Paper
PhoneConversation
VideoConversation
Face-to-faceConversation
Face-to-faceAt whiteboard
© 2009 Trail Ridge Consulting, LLC
Engage the Team
40
© 2009 Trail Ridge Consulting, LLC
Engage the Team
41
© 2009 Trail Ridge Consulting, LLC
Scrum teams work together
42
© 2009 Trail Ridge Consulting, LLC
Engage the Team
43
© 2009 Trail Ridge Consulting, LLC
Scrum team share space
44
© 2009 Trail Ridge Consulting, LLC 45
Release Planning
0
40
80
120
160
Jan Feb Mar Apr May Jun Jul Aug Sep
Points
② Relative Estimation
③ Prioritization ④ Velocity Projection
① Project Definition
© 2009 Trail Ridge Consulting, LLC 46
Story Identification
②Brainstorm user stories for each theme
①List the primary objectives or themes for the release
Theme 1 Theme 2 Theme 4 Theme 5Theme 3
Story 22
Story 14
Story 18
Story 5
Story 12
Story 9
Story 13
Story 21 Story 16
Story 10
Story 3
Story 7
Story 2
Story 18
© 2009 Trail Ridge Consulting, LLC
Release by Theme
47
© 2009 Trail Ridge Consulting, LLC
Release Plan as a Team
48
© 2009 Trail Ridge Consulting, LLC 49
Relative Estimation
①Layout the
stories relatively
1 2 3 5 8 13
②Group into
point values
Story 225 pt
Story 145 pt
Story 181 pt
Story 58 pt
Story 128 pt
Story 93 pt
Story 131 pt
Story 212 pt
Story 1613 pt
Story 103 pt
Story 35 pt
Story 78 pt
Story 25 pt
Story 181 pt
© 2009 Trail Ridge Consulting, LLC
Relative Estimation
50
© 2009 Trail Ridge Consulting, LLC
Relative Estimation by Team
51
© 2009 Trail Ridge Consulting, LLC
Velocity Projection
52
Jan 1 Jan 2 Feb 1 Feb 2
Story 225 pt
Story 145 pt
Story 181 pt
Story 58 pt
Story 128 pt
Story 93 pt
Story 131 pt
Story 212 pt
Story 1613 pt
Story 103 pt
Story 35 pt
Story 78 pt
Story 25 pt
Story 181 pt
Mar 1 Mar 2
Use only to estimate velocity - not to create a locked plan. Just keep the priorities sorted in the backlog
© 2009 Trail Ridge Consulting, LLC
Release Plan
53
© 2009 Trail Ridge Consulting, LLC
Release Plan
54
© 2009 Trail Ridge Consulting, LLC
Velocity Estimation as a Team
55
© 2009 Trail Ridge Consulting, LLC
Sprint Planning
56
Story 22 Story 5 Story 9 Story 13 Story 10
① Identify the next priority stories and post them on the wall or task board
• AC 1• AC 2
• AC 1• AC 2
• AC 1• AC 2
② Review the acceptance criteria of each story, or identify them if not done
CodeCode
TestTest
Doc
UXMeet
CodeCode
TestTest
Doc
UXMeet
CodeCode
TestTest
Doc
UXMeet
③Allow the team to brainstorm all tasks and hours for all stories at once - not one at a time
④Review all results looking for missing tasks, wrong sizes, and gaining commitment
© 2009 Trail Ridge Consulting, LLC
Sprint Planning
57
© 2009 Trail Ridge Consulting, LLC
Sprint Planning
58
© 2009 Trail Ridge Consulting, LLC
5 Min Review
59
① Focus ② Timebox
③ Visualize ④ Engage the Team
Strategic Tactical
© 2009 Trail Ridge Consulting, LLC
5 Min Session Retrospective
What worked well?
60
What would you change?
top related