Page 1
Chair of Software Engineering for Business Information Systems (sebis)
Faculty of Informatics
Technische Universität München
wwwmatthes.in.tum.de
The Evolution of Scaling Agile PracticesFinal Presentation: Bachelor Thesis, Gerhard Schwab, 23.10.2017, Munich
Page 2
Motivation
Research Approach
Related Work
Main Contribution
Survey Results
Limitations
Conclusion & Future Work
Outline
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 2
Page 3
• Digitization higher demand for adaptability
• Manage changing priorities
• Increase productivity
• Improve project visibility
• Less time to market
Motivation
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 3
VersionOne2017: 11th annual State of Agile™ survey .
High demand for agile practices
0%
10%
20%
30%
40%
50%
60%
70%
80%
90%
100%
Practicing agile >50% of teams agile Realized success Clash with culture
Page 4
• What about scaling agile practices?
• Designed for numerous teams
Working together on 1 project
• All benefits of agile practices
• Change & improvement of
Company culture
Motivation
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 4
VersionOne2017: 11th annual State of Agile™ survey .
High demand for scaling agile practices
0%
10%
20%
30%
40%
50%
60%
70%
80%
90%
100%
Practicing agile <50% of teams agile Realized success Clash with culture
Page 5
Motivation
Research Approach
Related Work
Main Contribution
Survey Results
Limitations
Conclusion & Future Work
Outline
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 5
Page 6
RQ1: Which scaling agile practices exist?
RQ2: How did scaling agile practices develop?
RQ3: On which foundational methods and practices are scaled agile practices
based on?
Research Approach
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 6
Page 7
Research Approach: Literature review
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 7
Page 8
Research Approach: Questionnaire
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 8
Page 9
Motivation
Research Approach
Related Work
Main Contribution
Survey Results
Limitations
Conclusion & Future Work
Outline
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 9
Page 10
• P. Abrahamsson: Agile Software Development Methods: Review and Analysis 2002
• Aggregation of Agile Software Development Methods
• D. Cohen: Agile Software Development 2003
• Aggregation of Agile Software Development Methods
• A. Vaidya: Does DAD Know Best, Is it Better to do LeSS or Just be SAFe? 2014
• Description of different Scaling Agile Practices
• Ö. Uludag: Investigating the Role of Architects in Scaled Agile Frameworks
• Foundation of this work
Related Work
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 10
Page 11
Motivation
Research Approach
Related Work
Main Contribution
Survey Results
Limitations
Conclusion & Future Work
Outline
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 11
Page 12
Agile Software Solution Framework (ASSF)
Crystal Family (Crystal)
Disciplined Agile 2.0 (DA 2.0)
Dynamic Systems Development Method Agile Project Framework for Scrum (DSDM)
Enterprise Scrum (eScrum)
Enterprise Transition Framework (ETF)
Event Driven Governance
eXponential Simple Continuous Autonomous Learning Ecosystem (XSCALE)
FAST Agile
Holistic Software Development (HSD)
Large Scale Scrum (LeSS)
Lean Enterprise Agile Framework (LEAF)
Matrix of Services (Maxos)
Mega Framework (Mega)
Nexus
Recipes for Agile Governance in the Enterprise (RAGE)
Resilient Agile
Scaled Agile Framework (SAFe)
ScALeD Agile Lean Development (SALD)
Scrum at Scale (S@S)
Scrum-of-Scrums(SoS)
Spotify Model (Spotify)
Research Outcome
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 12
Page 13
Research Outcome
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 13
Page 14
Holistic Software Development HSD
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 14
Page 15
Holistic Software Development HSD
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 15
Page 16
• Split project into use case boundaries
• Sunny/Rainy Day analysis of use cases
• Increases planning by extensive prototyping
• Cuts unnessecary meetings/ overhead
• Can be used with any process of delivering code, like Scrum
Resilient Agile
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 16
Page 17
Resilient Agile
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 17
Page 18
Research Outcome
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 18
Page 19
Research Outcome - Methods
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 19
Page 20
Research Outcome - Practices
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 20
Page 21
Research Outcome - Activities
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 21
Page 22
Research Outcome - Artifacts
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 22
Page 23
Research Outcome - Principles
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 23
Page 24
Motivation
Research Approach
Related Work
Main Contribution
Survey Results
Limitations
Conclusion & Future Work
Outline
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 24
Page 25
Participation
Finished survey (5) Did not finish survey (7) Invited, but did not reply (9)
Survey Results
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 25
Page 26
Example Questions:
• On which level does your scaling agile practice
scale?
Survey Results
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 26
• How would you categorzie your scaling agile
practice?
0
1
2
3
4
5
6
7
8
Team Programm Portfolio IT Organization Enterprise
0
1
2
3
4
5
6
7
8
Page 27
Example Questions:
• Do you plan to continue developing your scaling
agile practice?
Survey Results
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 27
• What is the idea behind your scaling agile
practice and what problems does it mainly
address?:
“Combining the philosophies of agile and
lean with organisational workflow to
achieve whole organisation agility. HSD
bridges the traditional business
management world with software agility
in teams, without compromising the goals
of either. Focussing on cross-team
integration, delivering value and
embracing change at all levels of the
business HSD provides a framework for
organisations to make positive, people-
centric change.” HSD
Yes No
Page 28
Motivation
Research Approach
Related Work
Main Contribution
Survey Results
Limitations
Conclusion & Future Work
Outline
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 28
Page 29
• No comparison, only description
• Grouping frameworks useful?
• Survey
• Roles not asked
• Optimal tool?
• Duration (ongoing?)
• Relations to developers
• Missing contact data
• Only snapshot of 2017
Limitations
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 29
Page 30
Motivation
Research Approach
Related Work
Main Contribution
Survey Results
Limitations
Conclusion & Future Work
Outline
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 30
Page 31
• Identified 22 scaling agile practices
• Successfull rank practices by chronological order
• Gained insight into mentality and view point of developers via survey
• Conducted survey:
• ~50% accepted invitation
• Only ~25% finished Better optimized survey needed
Conclusion
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 31
Page 32
• Thesis only a snapshot of 2017
• Scaling agile „market“ changes rapidly
Update in the future possible
• „Upgrade“ the survey:
More developers?
Keep running?
Different process?
Different Tools?
• Comparison of Scaling Agile Practices
Future Work
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 32
Page 33
Thank you for your attention!
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 33
Page 34
Research Roadmap
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 34
2017 2017Jun Jul Aug Sep Okt Nov
Kick-Off Presentation24/7/17
Final Presentation23/10/17
22/6/17 - 25/8/17Literature Review
27/7/17 - 17/8/17Questionnaire
18/08/17 - 28/09/17Interviews
10/08/17 - 20/10/17Graphics
15/6/17 - 31/10/17Writing
Page 35
• Which scaling agile practice did you develop?
• What is the idea behind your scaling agile practice and what problems does it mainly address?
• How would you categorize your scaling agile practice?
• What outcomes are expected after using your scaling agile practice?
• On which level does your scaling agile practice scale?
• What are the major challenges, problems, and misunderstandings in implementing and using your practice?
• When did you start with the creation of your scaling agile practice?
• When did you publish or release the first version of your scaling agile practice?
• How many releases does your scaling agile practice have and when were they released?
• Do you plan to continue developing your scaling agile practice?
• Why do you want to stop the further development of your scaling agile practice?
• What is your advice for people interested in your scaling agile practice, which is not developed anymore?
Should they continue to use it or should they use other scaling agile practices?
Survey Questions
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 35
Page 36
• What agile activities does your scaling agile practice use?
• What agile methods does your scaling agile practice use?
• What agile practices does your scaling agile practice use?
• What agile artifacts are used in your scaling agile practice?
• What principles does your scaling agile practice employ?
• What differentiates your scaling agile practice from others?
• With which other scaling agile practices can your scaling agile practice be combined? Are there major
problems involved in combining? Are there major gains for combining?
• What are the main changes between your scaling agile practice versions and were they influenced by other
scaling agile practices?
• Is there anything your scaling agile practice is incompatible with?
• Do you have further remarks or some points to add?
Survey Questions
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 36
Page 37
• ASSF: Framework & Mechanism
• ETF: Set of Principles
• FAST: Mechanism
• HSD: Framework
• LeSS: Organizational Design
• Mega: Framework
• Nexus: Framework
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 37
Page 38
HSD
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 38
Page 39
Research Outcome - ASSF
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 39
Page 40
Research Outcome - Crystal
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 40
Page 41
Research Outcome – DA2.0
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 41
Page 42
Research Outcome - DSDM
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 42
Page 43
Research Outcome - eScrum
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 43
Page 44
Research Outcome - ETF
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 44
Page 45
EDG
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 45
Page 46
• eXponential Return
• Increase Rate of ROI (ROROI)
• Simple Design
• Continuous Throughput
• Autonomous Teams
• Learning: triple loop
• What? How? Why?
• Ecosystems Thinking (Whole Board Thinking)
• What is the most important descicion to make next?
Xscale
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 46
Page 47
• Build around 1 central meeting:
1. Present completed work
2. Volunteers pick next stories/ problems
3. Public announcments/ vision realignment
4. Build teams based on 2.
• Influenced by Open Space Technology
Requires co-location
FAST
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 47
Page 48
LeSS
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 48
Page 49
LEAF
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 49
Page 50
Maxos
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 50
Page 51
Mega
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 51
Page 52
Nexus
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 52
Page 53
Rage
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 53
Page 54
SAFe 4.5
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 54
Page 55
Excited Customers:
• Define Value and how it is Created (shared
understanding)
• Produce small, deliverable increments
Happy and Productive Employees:
• Create Independent, Cross-functional Teams
• Authorize and Empower your Employees
Global Optimization:
• Create Transparency in all Directions
• Prefer Direct Communication
• Create Flow and Rythm
ScALeD
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 55
Supportive Leadership:• Set Objectives and Provide Support
• Decentralize Control Structures
• Cultivate the Change and Change the
Culture
Continuous Improvement:• Inspect and Adapt the Product
• Inspect and Adapt the Development
Process
• Inspect and Adapt the Organisation
Page 56
S@S
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 56
Page 57
SoS
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 57
Page 58
Spotify
© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 58