the evolution of scaling agile practices - sebis tu münchen · the evolution of scaling agile...

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

Motivation

Research Approach

Related Work

Main Contribution

Survey Results

Limitations

Conclusion & Future Work

Outline

© sebis171023 Gerhard Schwab Bachelor Thesis Final Presentation 2

• Digitization higher demand for adaptability

• Manage changing priorities

• Increase productivity

• Improve project visibility

• Less time to market

Motivation


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

• 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


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

Motivation

Research Approach

Related Work

Main Contribution

Survey Results

Limitations


Outline


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


Research Approach: Literature review


Research Approach: Questionnaire


Motivation

Research Approach

Related Work

Main Contribution

Survey Results

Limitations


Outline


• 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


Motivation

Research Approach

Related Work

Main Contribution

Survey Results

Limitations


Outline


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


Research Outcome


Holistic Software Development HSD


• 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


Resilient Agile


Research Outcome


Research Outcome - Methods


Research Outcome - Practices


Research Outcome - Activities


Research Outcome - Artifacts


Research Outcome - Principles


Motivation

Research Approach

Related Work

Main Contribution

Survey Results

Limitations


Outline


Participation

Finished survey (5) Did not finish survey (7) Invited, but did not reply (9)

Survey Results


Example Questions:

• On which level does your scaling agile practice

scale?

Survey Results


• 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

Example Questions:

• Do you plan to continue developing your scaling

agile practice?

Survey Results


• 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

Motivation

Research Approach

Related Work

Main Contribution

Survey Results

Limitations


Outline


• 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


Motivation

Research Approach

Related Work

Main Contribution

Survey Results

Limitations


Outline


• 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


• 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


Thank you for your attention!


Research Roadmap


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

• 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


• 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


• ASSF: Framework & Mechanism

• ETF: Set of Principles

• FAST: Mechanism

• HSD: Framework

• LeSS: Organizational Design

• Mega: Framework

• Nexus: Framework


HSD


Research Outcome - ASSF


Research Outcome - Crystal


Research Outcome – DA2.0


Research Outcome - DSDM


Research Outcome - eScrum


Research Outcome - ETF


EDG


• 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


• 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


LeSS


LEAF


Maxos


Mega


Nexus


Rage


SAFe 4.5


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


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

S@S


SoS


Spotify


the evolution of scaling agile practices - sebis tu münchen · the evolution of scaling agile...

Documents