Guided Research: Identifying and Structuring Challenges in ... · P S2 Concerns e.g. agile team enterprise architect product owner e.g. reduce team dependencies, building an evolvable

Chair of Software Engineering for Business Information Systems (sebis)

Faculty of Informatics

Technische Universität München

wwwmatthes.in.tum.de

Guided Research: Identifying and Structuring Challenges in

Adopting Agile and Lean Practices in Large Organizations based

on a Literature AnalysisChristoph Caprano, Guided Research, Final Presentation, 23/04/2018

Motivation

Research Questions

Research Approach

Key Findings

Summary & Outlook

Outline

© sebisGR Caprano - Identifying and Structuring Large-Scale Agile Challenges 2

Motivation (1)


AGILE

Req. Engineer

Concerns

Motivation (2)

Stakeholders

C1

?C2

?C4

?

SolutionsM1 P1

!

Bjarnason et al. Angelov et al.

Architect

C5

?C6

?C7

?

Paasivaara & LasseniusDikert et al.

C3

?

M2

Pattern Language

GR Caprano - Identifying and Structuring Large-Scale Agile Challenges © sebis 4

C8

?C9 C10

??

M3 M4

Motivation (3)

© sebis 5

Programs

Stakeholders

Viewpoint patterns

Information model

patterns

Vie

ws / A

rtifacts

DC1

C1

?

V2

123

V3

Report

V1

I1 I3

DC2

S3

I2

DC3

C2

?C3

?

P S2

Concerns

e.g. agile team

enterprise architect

product owner

e.g. reduce team dependencies,

building an evolvable architecture

e.g. context map,

sprint dependency matrix

e.g. business domains,

team epics,

bounded contexts

e.g. import daily from Jira

Method patterns

Architecture principles

e.g. domain modeling,

high flexibility, efficiency and

modularity of architectural solutionsM1 AP1

!

Influence factors

Maturity levels I2 ML1

e.g. time-to-market,

portfolio level,

program level

Data collection patterns

I1

GR Caprano - Identifying and Structuring Large-Scale Agile Challenges

Motivation

Research Questions

Research Approach

Key Findings

Summary & Outlook

Outline


Research Questions


Which stakeholders exist in large-scale agile development endeavors?RQ1

What are challenges of stakeholders and programs in large-scale agile

development efforts?RQ2

Which challenge categories are the most salient in large-scale agile

development?RQ3

What are generalizable findings on stakeholder- and program-related

challenges in large-scale agile development endeavors?RQ4

Motivation

Research Questions

Research Approach

Key Findings

Summary & Outlook

Outline

© sebis 8GR Caprano - Identifying and Structuring Large-Scale Agile Challenges

Placement in the development of the new LSAPC


Development of a concept for

large-scale agile best practices

Evaluating the LSAPC 2019

concept with expert interviews

1. CONCEPT DEVELOPMENT

Collection of existing practical

knowledge of large-scale agile

challenges and practices

2. DATA COLLECTION

3. EVALUATION

Online survey on the usage of

large-scale agile patterns in

practice

4. MAIN STUDY

Analysis of the survey results

and publication of the LSAPC

5. PUBLICATION

Deliverable: Final LSAPC 2019

ReportDeliverable: Evaluation of the

LSAPC 2019 concept

Deliverable: Concept for the LSAPC

2019

Deliverable: Challenges and Pattern

candidates

Deliverable: Large-scale agile

pattern usage in practice

Literature Review

ASAP Workshops

Case Studies

2015

Large-Scale Agile Pattern Catalog

2019

Research Approach


Database #Papers

IEEE 100

ACM 156

External 6

RQ1RQ2

RQ3Abstract,

Title

Portfolio-Mger

Scrum Master

Product

Owner

Scrum Master

Software

Architect

Methodology

Software-

Architecture

- Challenge A

- Challenge B

- Challenge C

- Challenge D

- Challenge E

- Challenge A

- Challenge B

- Challenge C

- Challenge D

- Challenge EMethodology

Software-

Architecture

2. Coding

1. Structured Literature Review Scrum Master

Product Owner

Portfolio-Mger

3. Refinement 4. Analysis

Duplicate

Duplicate

("large" or scal* or transform*) and

("lean" or "agile“) and

("challenge" or "concern" or "problem")

and "software"

Database #Papers

IEEE 22

ACM 45

External 6RQ4

Exkurs: MAXQDA Coding

© sebis161208 Matthes English Master Slide Deck (wide) 11

Motivation

Research Questions

Research Approach

Key Findings

Summary & Outlook

Outline

© sebisGuided Research: Identifying Large-Scale Agile Challenges and Best Practices 12

Key Findings


Name Example # Identified Elements

Stakeholders Product owner, scrum master 14

Challenges Ensuring that non-functional requirements are considered

by the development team

79

M-Patterns Scrum of scrums, community of practices 122

Architectural Principles Reuse of functionalities, buy before make 4

V-Patterns Burndown chart, context map 9

Anti-Patterns Don’t put individual goals over team goals 17

Key Findings (2)

© sebis 14

Programs

Stakeholders

Viewpoint patterns

Information model

patterns

Vie

ws / A

rtifacts

DC1

C1

?

V2

123

V3

Report

V1

I1 I3

DC2

S3

I2

DC3

C2

?C3

?

P S2

Concerns

e.g. agile team

enterprise architect

product owner

e.g. reduce team dependencies,

building an evolvable architecture

e.g. context map,

sprint dependency matrix

e.g. business domains,

team epics,

bounded contexts

e.g. import daily from Jira

Method patterns

Architecture principles

e.g. domain modeling,

high flexibility, efficiency and

modularity of architectural solutionsM1 AP1

!

Influence factors

Maturity levels I2 ML1

e.g. time-to-market,

portfolio level,

program level

Data collection patterns

I1

RQ1

RQ2

ID Name # Documents

S-2 Enterprise Architect 3

S-3 Program Manager 4

S-4 Business Analyst 3

S-5 Support Engineer 2

S-7 Development Team 50

S-8 Product Owner 33

S-11 UX Expert 1

S-13 Agile Coach 4

S-14 Solution Architect 2

S-16 Test Team 18

S-17 Software Architect 21

S-19 Scrum Master 30

S-20 Portfolio Manager 2

ID Name Category Novelty Affected

stakeholders or

program

#Origins

C-1 Ensuring that non-

functional

requirements are

considered by the

development team

Software-Architecture Yes Software Architect,

Solution Architect

6

C-2 Creating precise

requirement

specifications for the

development team

Requirements

Engineering

No Product Owner 3

C-3 Managing and

integrating

heterogenous

subsystems of

different

development teams

Software Architecture Yes Solution Architect 1

C-4 Defining a

lightweight formal

review process for

new technologies

Enterprise Architecture Yes Enterprise Architect 4


© sebis 15

M51

Common planning and

retrospective meetings

Communicating business

requirements to development

team

C-32

?

C-47

?

V2

Collaborative Scrum

Board

Defining clear and visible prioritiesSharing

common vision

C-42

?

Key Findings - Example


…

Product Owner

S3

© sebis 16

M65

Scheduling additional

efforts for addressing

technical debts

Budgeting additional

efforts for addressing

technical debts

Incorporating a dedicated

architect role in the large-

scale agile development

program

M113M66

Managing technical debts

C-41

?

M42

Feature Analysis

Workshop

Creating a proper upfront

architecture design of the system

C-44

?

Key Findings – Example(2)


…

Software Architect

S3

Key Findings - Categorization

© sebis 17

• C-40 Facilitating shared context and

knowledge

• C-42 Sharing common vision

• C-52 Establishing a common scope for

different stakeholder groups

• C-54 Creating lightweight

documentation

• C-91 Dealing with internal silos


© sebis 18

Key Findings – Observations

Architecture becomes more important the more complex the task or system is

New stakeholder roles are involved when scaling agile development

Scaling agile development entails new communication and coordination challenges

Challenges in agile development still exist in large-scale agile development

Stakeholders that are successfully isolated by the scrum master from external influences have less

concerns in large-scale agile development.

1

2

3

4

5


Motivation

Research Questions

Research Approach

Key Findings

Summary & Outlook

Outline


Summary


C1

?

V2

123

V3

Report

V1

S3

C2

?C3

?

S1 S2

M1 P1

!

14 Stakeholders

69 Challenges in

11 Topics

122 M-Patterns &

17 Anti-Patterns &

7 Architectural Principles

9 V-Patterns

+

Architecture becomes more important the more

complex the task or system is

New stakeholder roles are involved when scaling

agile development

Scaling agile development entails new

Communication and coordination challenges

Challenges in agile development may still exist

in large-scale agile development

Stakeholders that are successfully isolated by

the scrum master from external influences have less

concerns in large-scaled agile development.

Outlook


Development of a concept for

large-scale agile best practices

Evaluating the LSAPC 2019

concept with expert interviews

1. CONCEPT DEVELOPMENT

Collection of existing practical

knowledge of large-scale agile

challenges and practices

2. DATA COLLECTION

3. EVALUATION

Online survey on the usage of

large-scale agile patterns in

practice

4. MAIN STUDY

Analysis of the survey results

and publication of the LSAPC

5. PUBLICATION

Deliverable: Final LSAPC 2019

ReportDeliverable: Evaluation of the

LSAPC 2019 concept

Deliverable: Concept for the LSAPC

2019

Deliverable: Challenges and Pattern

candidates

Deliverable: Large-scale agile

pattern usage in practice

Literature Review

ASAP Workshops

Case Studies

2015

Large-Scale Agile Pattern Catalog

2019

Technische Universität München

Faculty of Informatics

Chair of Software Engineering for Business

Information Systems

Boltzmannstraße 3

85748 Garching bei München

Tel +49.89.289.

Fax +49.89.289.17136

wwwmatthes.in.tum.de

Christoph Caprano

B.Sc.

17132

[email protected]

http://wwwmatthes.in.tum.de/

Backup


Backup: MAXQDA (1)


Backup: MAXQDA (2)


Backup: MAXQDA (3)


Backup: MAXQDA (4)


Key Findings - Stakeholders


Which stakeholders exist in large-

scale agile projects? RQ1

Key Findings – Concerns


What are project- or stakeholder

specific challenges/concerns?RQ2

Key Findings – Topics


How can the challenges be

categorized?RQ3

Key Findings – M-Pattern Candidates


AdditionalsRQ?

Key Findings – V-Pattern Candidates


AdditionalsRQ?