Scrum, but…? Scrum, and…! Using Scrum and Requirements Engineering Successfully
Susanne Muehlbauer
02 September 2011
HOOD GmbH
August 2011
Content
Aims & Basics
• Why Agile SW-Development?
• Some Basics for Scrum
• Is RE necessary in an agile Environment?
Scrum & RE
• Where can we find RE in Scrum?
• Which RE-Methods can we use in Scrum?
Questions & Answers
-2- Copyright © 2011 HOOD Ltd.http://www.HOOD-Group.com Confidential.
Transmission or reproduction prohibited in any form or by any means without
the prior permission of HOOD GmbH. -2-
HOOD GmbH
August 2011
Aims & Basics
• Why Agile SW-Development?
• Some Basics for Scrum
• Is RE necessary in an agile Environment?
-3- Copyright © 2011 HOOD Ltd.http://www.HOOD-Group.com Confidential.
Transmission or reproduction prohibited in any form or by any means without
the prior permission of HOOD GmbH. -3-
HOOD GmbH
August 2011
The Software Factory
Good idea, but...
Copyright © 2011 HOOD Ltd.http://www.HOOD-Group.com Confidential.
Transmission or reproduction prohibited in any form or by any means without
the prior permission of HOOD GmbH.
-4-
... the wrong Analogy!
-4-
HOOD GmbH
August 2011
Software-Development is complex
Copyright © 2011 HOOD Ltd.http://www.HOOD-Group.com Confidential.
Transmission or reproduction prohibited in any form or by any means without
the prior permission of HOOD GmbH.
-5-
Source: Ken Schwaber: Agiles Projektmanagement mit Scrum. Microsoft Press 2007 (ISBN 978-3-86645-631-0)
-5-
HOOD GmbH
August 2011
Heavyweight goes agile
Source: www.enjoyart.com
Copyright © 2011 HOOD Ltd.http://www.HOOD-Group.com Confidential.
Transmission or reproduction prohibited in any form or by any means without
the prior permission of HOOD GmbH.
-6-
Float like a
butterfly,
and sting like a bee -6-
HOOD GmbH
August 2011
Agile Manifesto
Copyright © 2011 HOOD Ltd.http://www.HOOD-Group.com Confidential.
Transmission or reproduction prohibited in any form or by any means without
the prior permission of HOOD GmbH.
-7-
Source: nach http://agilemanifesto.org/iso/de/
-7-
HOOD GmbH
August 2011
Agile Values
Copyright © 2011 HOOD Ltd.http://www.HOOD-Group.com Confidential.
Transmission or reproduction prohibited in any form or by any means without
the prior permission of HOOD GmbH.
-8-
Source: www.burn-out-forum.de/forum/viewtopic.php?f=3..
Courage,
Communication,
Simplicity,
Feedback,
Transparency,
Openess,
Trust,
Respect -8-
HOOD GmbH
August 2011
And now...?
Copyright © 2011 HOOD Ltd.http://www.HOOD-Group.com Confidential.
Transmission or reproduction prohibited in any form or by any means without
the prior permission of HOOD GmbH.
-9-
Source: http://annieinfinite.com/wp-content/uploads/2009/10/then-a-miracle-occurs-cartoon.png
The Agile Manifesto does not tell us
about Methods and Processes
-9-
HOOD GmbH
August 2011
The Agile Manifesto – Implementations
Copyright © 2011 HOOD Ltd.http://www.HOOD-Group.com Confidential.
Transmission or reproduction prohibited in any form or by any means without
the prior permission of HOOD GmbH.
-10-
Source: nach http://agilemanifesto.org/iso/de/
Known agile
Frameworks:
XP
FDD
Crystal
Scrum
...
Known agile
Methods:
Pair Programming
Refactoring
Personas
Continuous Integration
...
Product Backlog
CI AufsetzenVersionskontrolle
aufsetzenDB-Struktur
anlegen
Sprint Backlog Sprint Auslieferbares
Produktinkrement
Daily Scrum
Maximal 30 Tage
24 stunden
ID Anforderung Akzeptanz-
kriterien
Prio
UR1 Als Standardbenutzer
möchte ich
3
UC2 Buch finden 2
UC3 Author hinzufügen 4
UR4 Als Author möchte ich 1
UR5 Als Standardbenutzer
möchte ich
5
UC6 Buch hinzufügen 7
UC7 In den Einkaufswagen 8
Scrum
-10-
HOOD GmbH
August 2011
Copyright © 2011 HOOD Ltd.http://www.HOOD-Group.com Confidential.
Transmission or reproduction prohibited in any form or by any means without
the prior permission of HOOD GmbH.
* “Agile Software Development with scrum”, Ken Schwaber, Microsoft Press, 2004
** „Scrum guide“, Scrum Alliance, http://www.scrumalliance.org/resource_download/598
The idea of Scrum
-11-
HOOD GmbH
August 2011
3 Roles
Copyright © 2011 HOOD Ltd.http://www.HOOD-Group.com Confidential.
Transmission or reproduction prohibited in any form or by any means without
the prior permission of HOOD GmbH.
Product
Owner
Product
Backlog
Value/ ROI
Order/ Prioritisation
Development
Team
Implementation
Cross functional
Self organizing
Scrum
Master
Servant-Leader
Techniques,
Practices,
Rules
Impediments
-12-
HOOD GmbH
August 2011
3 Artifacts
Copyright © 2011 HOOD Ltd.http://www.HOOD-Group.com Confidential.
Transmission or reproduction prohibited in any form or by any means without
the prior permission of HOOD GmbH.
Product
Backlog
Backlog Items
Ordered/Prioritized
Estimated
Sprint
Backlog
Selected
Backlog Items
unchangeable
Commited
Burndown
Chart
Progress
Source: „ http://blog.mountaingoatsoftware.com/improving-on-traditional-release-burndown-charts“
-13-
HOOD GmbH
August 2011
3 Meetings/ Events
Copyright © 2011 HOOD Ltd.http://www.HOOD-Group.com Confidential.
Transmission or reproduction prohibited in any form or by any means without
the prior permission of HOOD GmbH.
Sprint
Planning
Why
What
How
Daily
Scrum
Inspect &
Adapt
Communication
Focus
Review
Retro
Results
Development
Process
Inspect &
Adapt
-14-
HOOD GmbH
August 2011
Scrum & RE
• Where can we find RE in Scrum?
• Which RE-Methods can we use in Scrum?
Scrum Documentation [SUT10]:
[…] refining (or “grooming”) the Product Backlog:
This includes detailed requirements analysis, […]
Scrum is silent on how this work is done […]
Copyright © 2011 HOOD Ltd.http://www.HOOD-Group.com Confidential.
Transmission or reproduction prohibited in any form or by any means without
the prior permission of HOOD GmbH. -15-
HOOD GmbH
August 2011
Stakeholders
Scrum Team
Development Team
The Product Owner in the project organisation
Copyright © 2011 HOOD Ltd.http://www.HOOD-Group.com Confidential.
Transmission or reproduction prohibited in any form or by any means without
the prior permission of HOOD GmbH.
-16-
Scrum
Master
Product
Owner
Requirements
Engineering
Requirements
Engineering
HOOD GmbH
August 2011
-17-
• Product Backlog
• Clarification of Backlog Items
• Value of the work (ROI)
• Prioritization and
Order of Backlog Items
• Inspection of product
increments
• Release Planning
Being a Product Owner is a
full-time job
So
ruce
: h
ttp
://w
allp
ap
ers
-fre
e.c
o.u
k/b
ackg
rou
nds/c
art
oon
s/d
isn
ey/T
he
-In
cre
dib
les.jp
g
So
urc
e: h
ttp
://w
ww
.ga
mg
ea
.co
m/w
p-c
on
ten
t/up
loa
ds/2
00
9/0
4/t
he
-incre
dib
les-1
-siz
ed
1.jp
g
Responsibilities of the Product Owner
-17-
HOOD GmbH
August 2011
-18-
So
ruce
: h
ttp
://w
allp
ap
ers
-fre
e.c
o.u
k/b
ackg
rou
nds/c
art
oon
s/d
isn
ey/T
he
-In
cre
dib
les.jp
g
So
urc
e: h
ttp
://w
ww
.ga
mg
ea
.co
m/w
p-c
on
ten
t/up
loa
ds/2
00
9/0
4/t
he
-incre
dib
les-1
-siz
ed
1.jp
g
So
ruce
: h
ttp
://w
allp
ap
ers
-fre
e.c
o.u
k/b
ackg
rou
nds/c
art
oon
s/d
isn
ey/T
he
-In
cre
dib
les.jp
g
• Project Management
• Communication skills
• Know How within the
Business Domain
• Requirements Engineering
Being a Product Owner is a
challenging job
Capabilities of the Product Owner
-18-
HOOD GmbH
August 2011
Some Principles for Requirements Engineering in Scrum
1: Time boxing
Reducing the scope of the work to
a sprint of between two to four
weeks
2: Face-to-face
Communicating the requirements
through face-to-face conversation
of the Scrum team with the product
owner, who is available at all times
3: Deferred Decisions
Evolutionarily developing the
requirements as late as possible
(„deferred decisions‟ applied)
4: Embrace Change
Product Backlog does change,
Selected Backlog does not change
during the sprint
Copyright © 2011 HOOD Ltd.http://www.HOOD-Group.com Confidential.
Transmission or reproduction prohibited in any form or by any means without
the prior permission of HOOD GmbH. -19-
HOOD GmbH
August 2011
Where can we find RE in Scrum?
Copyright © 2011 HOOD Ltd.http://www.HOOD-Group.com Confidential.
Transmission or reproduction prohibited in any form or by any means without
the prior permission of HOOD GmbH.
Product
Vision
-20-
HOOD GmbH
August 2011
Product Vision - Example
„All my music is in my pocket“
Copyright © 2011 HOOD Ltd.http://www.HOOD-Group.com Confidential.
Transmission or reproduction prohibited in any form or by any means without
the prior permission of HOOD GmbH.
Apple
-21-
HOOD GmbH
August 2011
Agile Methods for the Product Vision
Copyright © 2011 HOOD Ltd.http://www.HOOD-Group.com Confidential.
Transmission or reproduction prohibited in any form or by any means without
the prior permission of HOOD GmbH.
Product • Feature • Feature • Feature
Elevator
Statement
Press Release
Vision Box
[COH06]
-22-
HOOD GmbH
August 2011
Requirements Engineering: Define Scope
Copyright © 2011 HOOD Ltd.http://www.HOOD-Group.com Confidential.
Transmission or reproduction prohibited in any form or by any means without
the prior permission of HOOD GmbH.
-23-
System Context
and
Interfaces
Stakeholder
Analysis
HOOD GmbH
August 2011
Where can we find RE in Scrum?
Copyright © 2011 HOOD Ltd.http://www.HOOD-Group.com Confidential.
Transmission or reproduction prohibited in any form or by any means without
the prior permission of HOOD GmbH.
-24-
Requirements
Acceptance
Business
and System
Requirements
HOOD GmbH
August 2011
Magic Backlog READY
Available
Ordered/
Prioritized
Estimated
INVEST
Understood
Source: http://www.birgit-helfmann.de/pict/wunderlampe.jpg
HOOD GmbH
August 2011
Release 3 Release 2 Release 1
From Vision to Product Backlog
Copyright © 2011 HOOD Ltd.http://www.HOOD-Group.com Confidential.
Transmission or reproduction prohibited in any form or by any means without
the prior permission of HOOD GmbH.
Vision
Business
Plan Business
Drivers
Minimum
Marketable
Product
Feature Feature Feature
Product
Backlog
User
Story
User
Story
User
Story
User
Story User
Story
User
Story
User
Story
-26-
Release
Planning
HOOD GmbH
August 2011
From Vision to Product Backlog
Copyright © 2011 HOOD Ltd.http://www.HOOD-Group.com Confidential.
Transmission or reproduction prohibited in any form or by any means without
the prior permission of HOOD GmbH.
Vision
Business
Plan Business
Drivers
Minimum
Marketable
Product
Feature Feature Feature
User
Story
User
Story
User
Story
User
Story User
Story
User
Story
User
Story
Organization Business
Processes
Constraints
Aufzugsystem
Fahrgast Wartungspersonal
Operator Energieversorgung
-27-
HOOD GmbH
August 2011
Requirements Engineering: Goal Modelling
Copyright © 2011 HOOD Ltd.http://www.HOOD-Group.com Confidential.
Transmission or reproduction prohibited in any form or by any means without
the prior permission of HOOD GmbH. -28-
HOOD GmbH
August 2011
RE: Activities
Elicit Specify
Copyright © 2011 HOOD Ltd.http://www.HOOD-Group.com Confidential.
Transmission or reproduction prohibited in any form or by any means without
the prior permission of HOOD GmbH. -29-
User
Story
Face-to-face Time boxing
HOOD GmbH
August 2011
Stakeholder/ User-Analysis
Copyright © 2011 HOOD Ltd.http://www.HOOD-Group.com Confidential.
Transmission or reproduction prohibited in any form or by any means without
the prior permission of HOOD GmbH.
Interest in Product/
Business Value
Stakeholder
Influence/ Power
Influence to
Product Success
High Low
Low
High
-30-
HOOD GmbH
August 2011
User Story Template
Copyright © 2011 HOOD Ltd.http://www.HOOD-Group.com Confidential.
Transmission or reproduction prohibited in any form or by any means without
the prior permission of HOOD GmbH.
Story Title
I as a X
Want Y
So that Z
[NORTH]
X is the person who will benefit from this story
being delivered.
Y is the content of the story.
Z is the benefit the story will deliver.
-31-
HOOD GmbH
August 2011
3 C„s for User Stories
Card
Just enough text to identify the requirement
Copyright © 2011 HOOD Ltd.http://www.HOOD-Group.com Confidential.
Transmission or reproduction prohibited in any form or by any means without
the prior permission of HOOD GmbH.
Conversation
Promise for a conversation between customer and programmer
Confirmation
Needs acceptance criteria
-32-
Story Titel
I as a X
Want Y
So that Z
Back side
Acceptance Criteria
HOOD GmbH
August 2011
-33-
„Grooming the Backlog“
• Detailed
Requirements
Analysis
• Splitting large items
• (Re-) Estimation
• (Re-) Prioritization
Quelle
: htt
p:/
/ww
w.p
fote
n-u
nd-c
o.d
e/f
oto
s/p
fle
geP
ferd
.jp
g
HOOD GmbH
August 2011
Level of Detail and Prioritization
Evolution of Requirements from Iteration to Iteration
Copyright © 2011 HOOD Ltd.http://www.HOOD-Group.com Confidential.
Transmission or reproduction prohibited in any form or by any means without
the prior permission of HOOD GmbH.
-34-
Source: WENN DER KUNDE NICHT WEISS, WAS ER WILL: TIPPS FÜR DEN AGILEN UMGANG MIT ANFORDERUNGEN, OBJEKTspektrum September/Oktober2009
Later
Versions
In Detail Analyzed
Requirements
Current
Iteration
Current
Version Roughly analyzed
Requirements
Order/ Priority
of Requirements
Iteration
Version
Deferred
Decisions
Embrace
Change
HOOD GmbH
August 2011
Prioritization
By Business Value
For the Customer
For the company (avoid costs, reduce costs)
By Stakeholders
By Themes
By MuSCoW
By Eisenhower (urgent/ important)
By risk
By Kano
Non-Functionl Aspects/ Architecture
Dependencies
Organizational requirements (e.g. Suppliers)
Time Restrictions (Launch Date)
Copyright © 2011 HOOD Ltd.http://www.HOOD-Group.com Confidential.
Transmission or reproduction prohibited in any form or by any means without
the prior permission of HOOD GmbH.
-35-
HOOD GmbH
August 2011
„INVEST in Good Stories“ Bill Wake
Sourc
e: w
ww
.energ
iezukunfts
chw
eiz
.ch/e
nerg
ie-fe
nste
r/img/fra
nken.jp
g
Quality Check
HOOD GmbH
August 2011
INVEST (Bill Wake)
I Independent
N Negotiable
V Valuable/ Vertical
E Estimable
S Small Sized right
T Testable
Copyright © 2011 HOOD Ltd.http://www.HOOD-Group.com Confidential.
Transmission or reproduction prohibited in any form or by any means without
the prior permission of HOOD GmbH.
-37-
Who is responsible for the compliance to the criteria?
HOOD GmbH
August 2011
Copyright © 2011 HOOD Ltd.http://www.HOOD-Group.com Confidential.
Transmission or reproduction prohibited in any form or by any means without
the prior permission of HOOD GmbH.
-38-
ww
w.k
ochfo
rm.d
e/a
rtik
elb
ilder/
Ka
ise
r_P
lus_T
ort
enstu
eck.jp
g
Story Splitting
ww
w.k
ochfo
rm.d
e/a
rtik
elb
ilder/
Ka
ise
r_P
lus_T
ort
enstu
eck.jp
g
HOOD GmbH
August 2011
The Example also works with Pizza...
htt
p:/
/4.b
p.b
logspot.
com
/_shlm
jgw
3V
ec/T
SZ
IjIK
7M
QI/
AA
AA
AA
AA
AC
A/L
R8a0LC
ozF
8/s
1600/p
izza.jp
g
-39-
HOOD GmbH
August 2011
Where can we find RE in Scrum?
Copyright © 2011 HOOD Ltd.http://www.HOOD-Group.com Confidential.
Transmission or reproduction prohibited in any form or by any means without
the prior permission of HOOD GmbH.
-40-
Implementation
Requirements
HOOD GmbH
August 2011
Team selects Backlog Items for Sprint Backlog
Copyright © 2011 HOOD Ltd.http://www.HOOD-Group.com Confidential.
Transmission or reproduction prohibited in any form or by any means without
the prior permission of HOOD GmbH.
-41-
Source: WENN DER KUNDE NICHT WEISS, WAS ER WILL: TIPPS FÜR DEN AGILEN UMGANG MIT ANFORDERUNGEN, OBJEKTspektrum September/Oktober2009
Later
Versions
In Detail Analyzed
Requirements
Current
Iteration
Current
Version Roughly analyzed
Requirements
Iteration
Version
Selected
Product
Backlog
Sprint
Backlog:
User Story
- Task
- Task
- Task
READY
State
Embrace
Change
Time boxing
HOOD GmbH
August 2011
Embrace Change
ww
w.f
lickr.
com
/photo
s/isdky/2
407964480/s
izes/l/in/p
hoto
str
eam
/
The Content of the Sprint Backlog is
stable!
No Changes/ no new
requirements during the current
spring (Iteration)
Short Iterations
Changes/ new requirements
become part of the product
backlog and will be prioritized
HOOD GmbH
August 2011
Agile Information Model
Copyright © 2011 HOOD Ltd.http://www.HOOD-Group.com Confidential.
Transmission or reproduction prohibited in any form or by any means without
the prior permission of HOOD GmbH.
-43-
Problem
Solution
Vision
Product Backlog
Sprint Backlog
SW Design Tasks
Backlog
Grooming
Planning I
Planning II
Why?
What?
How?
Levels Artifacts Activities
Responsible: PO
Involved: Team
Responsible: Team
Involved: PO
HOOD GmbH
August 2011
Where can we find RE in Scrum?
Copyright © 2011 HOOD Ltd.http://www.HOOD-Group.com Confidential.
Transmission or reproduction prohibited in any form or by any means without
the prior permission of HOOD GmbH.
-44-
Requirements
Acceptance
Release Planning
HOOD GmbH
August 2011
The Potentially releasable Product Increment
Every sprint must deliver a potentially releasable Product Increment
Every user story must be „Done“
The product increment must be „Done“
Definition of Done
Quality of the product increment
Non-functional requirements
Unit Tests
Refactoring
Deliverables oft the product increment, e.g.
Documentation
Installation Routine
Team-Specific
Copyright © 2011 HOOD Ltd.http://www.HOOD-Group.com Confidential.
Transmission or reproduction prohibited in any form or by any means without
the prior permission of HOOD GmbH.
-45-
HOOD GmbH
August 2011
Release-Planning
Copyright © 2011 HOOD Ltd.http://www.HOOD-Group.com Confidential.
Transmission or reproduction prohibited in any form or by any means without
the prior permission of HOOD GmbH.
-46-
Vision
Roadmap
Release Release
Sprint Sprint Sprint Sprint Sprint Sprint
Story 1
Story 7 Story 3 Story 9
Story 2 Story 4
...
t
Feature Feature Feature Feature Potentially
Releasable
Product
Increment
Feature Feature
Minimum Marketable Product Minimum Marketable Product
HOOD GmbH
August 2011
-47-
„Only Done is Done“ (Ralf Wirdemann)
Quelle: http://www.bauen-aber-richtig-weblog.de/wp-content/uploads/muenchen_giesinger_aussicht_baustelle.jpg
HOOD GmbH
August 2011
Can we find Requirements Engineering in Scrum?
1: Time boxing
Focus on a small amount of
requirements
Higher priority requirements are
clearer and have more detail than
lower priority requirements
2: Face-to-face
Communicating the requirements
through face-to-face conversation
3: Deferred Decisions
Evolutionarily developing the
requirements as late as possible
Differentiate between problem and
solution space
4: Embrace Change
… but before a requirement can be
taken into a sprint it has to have
enough detailed information and
acceptance criteria (ready state) Yes, Requirements Engineering is an important part of
Scrum.
Copyright © 2011 HOOD Ltd.http://www.HOOD-Group.com Confidential.
Transmission or reproduction prohibited in any form or by any means without
the prior permission of HOOD GmbH.
-48-
HOOD GmbH
August 2011
Questions & Answers
Are you ready for questions or are you done?
Copyright © 2011 HOOD Ltd.http://www.HOOD-Group.com Confidential.
Transmission or reproduction prohibited in any form or by any means without
the prior permission of HOOD GmbH.
-49-
HOOD GmbH
August 2011
Thank You!
Copyright © 2011 HOOD Ltd.http://www.HOOD-Group.com Confidential.
Transmission or reproduction prohibited in any form or by any means without
the prior permission of HOOD GmbH.
-50-
Susanne Muehlbauer
HOOD GmbH
Office Munich
Keltenring 7
82041 Oberhaching
Germany
Tel: 0049 89 4512 53 0
www.HOOD-Group.com
.,
HOOD GmbH
August 2011
Literature
[SUT10]
J. Sutherland, K. Schwaber (2010). The Scrum Papers: Nut, Bolts, and Origins of an Agile Framework.
[SCH10]
K. Schwaber, TraIning Material (2010), Professional Scrum Master, Scrum.org
[SUT11]
J. Sutherland, K. Schwaber (2011), Scrum Guide
[NORTH]
Dan North, Web Log
http://www.mountaingoatsoftware.com/system/presentation/file/11/SDBP05_AgileProductMgmt.pdf?1267636389
[COH06]
M. Cohn (2006), Agile Product Management,
http://www.mountaingoatsoftware.com/system/presentation/file/11/SDBP05_AgileProductMgmt.pdf?1267636389
[WAK03]
Bill Wake (2003), http://xp123.com/articles/invest-in-good-stories-and-smart-tasks/ Posted on August 17, 2003
[MOE11]
T. Mödl, S. Muehlbauer, Eine rationale Romanze, Objektspektrum, to be published 2011]
Copyright © 2011 HOOD Ltd.http://www.HOOD-Group.com Confidential.
Transmission or reproduction prohibited in any form or by any means without
the prior permission of HOOD GmbH.
-51-