'Scrum Mythbusters': Ilan Goldstein @ Colombo Agile Conference 2014
133
-
Upload
colombocampscommunity -
Category
Software
-
view
833 -
download
3
Transcript of 'Scrum Mythbusters': Ilan Goldstein @ Colombo Agile Conference 2014
Popularity of Agile Development
7th Annual State of Agile Development Survey 2013 by Version One (Sample size = 4048 respondents)
Organisations practicing Agile
84% 16%
More than 84% of respondents said their organisations were practicing Agile development, up from 80% in 2011 (sample size = 4048).
YES NO
3400 respondents
648 respondents
Scrum
Recognition
Implementation ?
Myth 1
S c r u m is an acronym
S C R U M Speaker Claims to Really Understand Myths
Tight, self-organising, collaborative teamwork
Ancient Spartan shield-locking phalanx
is an acronym
S C R U M
Myth 2
Sprints
S P E E D =
84%?
Agile processes promote
The team should be able to maintain a
sustainable development.
constant pace indefinitely
Agile Manifesto 8th principle
Focus Vs No end...
Feature
Sprints
S P E E D =
Myth 3
only for software
development
Scrum is an approach
Software???
Engineering???
§ Schools § Homes § Research § Training materials
SAAB Gripen Fighter Jet
WikiSpeed Car
only for software
development
Scrum is an approach
Myth 4
As a something user, I want to perform a certain function to achieve some benefit.
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on the right, we value the items on the
LEFT MORE. Thanks to: Agile Alliance
We don’t document, we’re agile!
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
That is, while there is value in the items on the right, we value the items on the
LEFT MORE. Thanks to: Agile Alliance
Not just 1 0 0 0 1 0 1 0 1 0 1 0 0 1 1 0 1 0 1 0 1 1 1 1 1 0 1 0 1 1 0 0 1 0 0 1 1 0 1 0 1 0 1 1 1 1 0 0 1 1 1 0 0 0 1
Code
Testing
Documentation
Audit
Support
User
Memory Control upfront
of detail at the Right level
right time
anti- documentation
Scrum is
Myth 5
User Story
Scrum teams must use the
format
As a something user, I want to perform a certain function to achieve some benefit.
Product Backlog Items
User Stories
Bugs
Technical Work
Knowledge Acquisition
The product backlog can be cosmopolitan
User Story
Scrum teams must use the
format
Myth 6
Planning Poker
Sprint Task Board Sprint Burndown Chart
Planning Poker
100 40 20 13 8
5 3 2 1 1 2
∞
Estimation is optional
Not Started
In Progress
Ready to Verify Done!!!
As a…… I want to…… So that……
As a…… I want to…… So that……
As a…… I want to…… So that……
Total hours of w
ork left to do on
expected days
300
270
240
210
180
150
120
90
60
30
0 1 2 3 4 5 6 7 8 9 10
Days
? Sprint Burndown
Total hours of w
ork left to do on
expected days
300
270
240
210
180
150
120
90
60
30
0 1 2 3 4 5 6 7 8 9 10
Days
Team tallies up duration of collective sprint tasks
Total hours of w
ork left to do on
expected days
300
270
240
210
180
150
120
90
60
30
0 1 2 3 4 5 6 7 8 9 10
Days
Daily tally
Total hours of w
ork left to do on
expected days
300
270
240
210
180
150
120
90
60
30
0 1 2 3 4 5 6 7 8 9 10
Days
Total hours of w
ork left to do on
expected days
300
270
240
210
180
150
120
90
60
30
0 1 2 3 4 5 6 7 8 9 10
Days
YOU GUYS SUCK! You’re already
behind and you’ve barely started!
Total hours of w
ork left to do on
expected days
300
270
240
210
180
150
120
90
60
30
0 1 2 3 4 5 6 7 8 9 10
Days
It’s not all bad….
Swarming
USE WITH CARE
are fundamental to Scrum
Planning Poker
Sprint Task Board Sprint Burndown
Myth 7
two weeks
Pre-work must fit into
Work before first delivery Sprint
Official
Mandated
Sprint Zero
Initial Product Backlog
Formulation
SM D PO
Vision Creation
Team Formation Sourcing Environments
Sprint 0
= 2 weeks???
FOR PURPOSE
F T I
two weeks
Pre-work must fit into
Myth 8
end
You must ship
or can only ship
at the
of every Sprint
Potentially shippable
increment product
Potentially
T E S
D
V A L I D T
D E M O N S T R E B L A T E D
Release after multiple sprints
Release every sprint
Release every feature
Scrum is no longer agile
enough!
At LEAST have
something potentially shippable
end
You must ship
or can only ship
at the
of every Sprint
Myth 9
Product Owner
Sprint Review is the event
to engage the
Scrum Team
D D D
D PO SM
SH SH SH
Broader stakeholder community
PO D
Walkthrough
G PASenerally G
ccepted A crum S
ractice P
Product Owner
Sprint Review is the event
to engage the
Myth 10
failure Sprint is a
when the team does not complete
everything in the Sprint Backlog
Sprint Backlog
Sprint Commitment =
Team commits to do their best
“ ”
SPRINT COMMITMENT
PLAN GUARANTEE ≠
PERFECT KNOWLEDGE
WHEN DONE =
Commitment
Forecast
Sprint
Is my Sprint a success or failure?
Success Failure
100% 0%
Team 1
0% 100%
Team 2
BONU
Constant accuracy is a false economy
Day Tester Programmer 1 Programmer 2
1
2
3
4
5
6
7
8
9
10
Test Design
Test Design
Test Design
Programming
Programming
Programming
Programming
Programming
Programming
Test Automation
Test Design
Test Automation Programming
Programming
Programming
Test Automation
Programming
Programming
Rework
Programming
Programming
Test Automation
Programming
Backlog Refinement
Exploratory Testing
Confirm Adjustments
Backlog Refinement
Walkthrough
Sprint Planning
Review and Retrospective Rework Rework
Walkthrough
Walkthrough
Exploratory Testing
Fear of over-extending
NEAR HORIZON PLANNING
Swarm to deliver product increments
Swarming
LESS
MORE
100% ACCURATE FORECAST
CULTURE OF
FEAR =
PLANNED
PLANNED
PLANNED
PLANNED
PLANNED
0% 100%
PLANNED
PLANNED
PLANNED
PLANNED
0% 100%
Sometimes over
EXTRA
Sometimes under
PLANNED
CONTINUOUS IMPROVEMENT
failure Sprint is a
when the team does not complete
everything in the Sprint Backlog
Myth 11
end-to-end
Requirement must
in the one Sprint
be completed
D D
D
D D
FUNCTIONAL DESIGN
TECHNICAL DESIGN
TEST DESIGN
DEVELOPMENT
TESTING
PB
I A
SP
RIN
T 3
Sprint...
often unpredictability =Functional
design
requires socialization
Delays
Waste
Confusion
end-to-end
Requirement must
in the one Sprint
be completed
Myth 12
cross- functional
All Scrum team
members must be
Design Team
Front-end Development
Team
Testing Team
Back-end Development
Team
TESTING
TECHNICAL WRITING
US
ER
EX
PE
RIE
NC
E
Can a UX designer
potentially conduct
some testing?
Teamwork
D
My bit is done, it’s your
problem now
D
cross- functional
All Scrum team
members must be
Final Myth...
D D
D
D D
SCRUMBUT
Scrum but We try to do we have to
conduct a testing Sprint from time to time
“ ”
Rome wasn’t built in a day!
SCRUMBUT
SCRUM IN PROGRESS
HYPOCRITICAL
Incrementally
iteratively improve
products
process of Scrum
&
not just our
but also the
It’s not about loops and lists...
Close feedback loops as soon as possible
Continuously improve both product & process
