what do practitioners vary in using scrum?
TRANSCRIPT
© Fraunhofer IESE
1
Philipp Diebold, Jan-Peter Ostberg, Stefan Wagner, and Ulrich Zendler
WHAT DO PRACTITIONERS VARY USING SCRUM?
@p_diebold
© Fraunhofer IESE
2
Motivation
75% of companies that claim usingScrum, do not really use Scrum
- K. Schwaber
© Fraunhofer IESE
3
MotivationScrumBut, but How and Why?
The following questions arise:
What do practitioners vary using Scrum?
Why do they vary it in this specific way?
ScrumBut
© Fraunhofer IESE
4
Case Study DesignGoal and Research Questions (RQs)
RQ1: What and why do they vary in the Development Team?
RQ1.1: What and why do they vary in the role of Product Owner?
RQ1.2: What and why do they vary in the role of Scrum Master?
RQ2: What and why do they vary in the Sprints?
RQ3: What and why do they vary in the events?
RQ4: What and why do they vary in requirements engineering?
RQ5: What and why do they vary in quality assurance?
Analyze Scrum to explore its industrial usage wrt. its variations from the perspective of practitioners.
© Fraunhofer IESE
5
Case Study DesignCase & Subject selection and description
Selection based on
Availability
Willingness
Maximize variation by
Number of employees (Start-Up to 130.000)
Different information system domains
International customers
Interview participant
Developers and dev. managers
10 Interviews
© Fraunhofer IESE
6
Results - Overview
7
© Fraunhofer IESE
7
Results – Team
General
often cross-functional teams
Generalists vs. Experts
Scrum team + Specification team
wide team range (from 2 to ~10)
8
© Fraunhofer IESE
8
Results – Team: Scrum Masterwide team range
(from 2 to ~10)
Used by most,to some extend
Different implementations
In combination with other role higher acceptance
General
often cross-functional teams
Generalists vs. Experts
Scrum team + Specification team9
Yes
Yes, but …
No
Used Scrum Master
© Fraunhofer IESE
9
Results – Team: Product Ownerwide team range
(from 2 to ~10)
Used by all,to some extend
Different implementations
In combination with other role higher acceptance
General
often cross-functional teams
Generalists vs. Experts
Scrum team + Specification team
50% use PO
Responsible for more teams
Split with other roles
10
Yes
Yes, but …
No
Used Product Owner
© Fraunhofer IESE
10
Results – Events: Daily ScrumMost often 15 min
Not always every day
Allow others to participate
Allow discussions
11
15 min
30 min
Yes
No
Duration
Discussion
© Fraunhofer IESE
11
Results - Sprint Length:
Fixed
1 – 4 weeks
Differing, e.g. „normal“ vs. clean-up Sprint
Exceptions are rare
Most often shielded from outside changes
Buffer:
Most often NOT calculated
If available, between 10% - 25%
15
2 weeks
3 weeks
4 weeks
varying
Length
None
Yes
Yes, <20%
Yes, >=20%Buffer
© Fraunhofer IESE
12
Dealing with Threats to Validity
State purpose and anonymity of interviews
answering honest and open
Usage of structured interview guidelines
helps structuring and during analysis
reduces risk of misinterpretation
Interview notes
review by participants
Used for re-extraction and discrepancies
Limited generalizability
mainly information system domains
only German companies
© Fraunhofer IESE
13
ConclusionResulting Statement
Our results show:
none of the companies conforms to the Scrum Guide (only one is close)
there is at least one company deviating from the standard foreach aspect.
Gave several reasons for their variations:
with pragmatic justifications, e.g. available resources
as legacy from hierarchical, non-agile processes
© Fraunhofer IESE
14
Questions?
Thank you
Philipp DieboldM. Sc.
Process Management
Dep. MPE
Fraunhofer IESEFraunhofer-Platz 1 | D-67663 Kaiserslautern
Phone: +49 (0) 631-6800-2183Fax: +49 (0) 631-6800-9-2183Email: [email protected]
© Fraunhofer IESE
15
Topics covered during the workshop will be, if not limited to:
A meta-model for the impact of Agile Practices (e.g., concepts, terms, relations, etc.) based on a proposal presented by the organizers
Elaborating and structuring existing impact of Agile Practices(e.g., SLRs, surveys, own experience, designing an own survey)
Plan for the (1) Collection of the impact of Agile Practices and (2) Operationalization of the impact of Agile Practices in practice
Dissemination / Publication of the impact of Agile Practices
ImpAct´151st International Workshop on the Impact of Agile Practices
24th August 2015, Tallinn
Co-located with
Important Dates:
June 30th, 2015 – Submission
August 24th, 2015 – Workshop Date
Sept. 30th, 2015 – Workshop Results
Organizers:Philipp [email protected]
Daniel Méndez Ferná[email protected]
Darja [email protected]
http://impact.iese.fraunhofer.de
Why to participate? (Benefits)
As researcher (e.g. PhD student), you cancontribute to a community working in the areaof combining agile software development withconcepts of knowledge bases (e.g. experiencebase) for decision support. Based on these ideas,papers or collaborations may emerge.
As practitioners, you get to know the currentstate-of-the-art for specific practices, ideas andimpacts of Agile Practices, and exchange withother practitioners and researchers.Additionally, we discuss on how tooperationalize and measure the impact.
How to participate? (Submissions)
We would be happy if you benefit from theoption to submit a short email statement ofintent to participate on the workshop [email protected].
We also provide the opportunity to brieflypresent your own experiences / contributionsand present it to all workshop participants (max.5 minutes). In this case, please inform us via mailas part of your statement to participate([email protected]).