Agile Manifesto and Practices Selection for Tailoring Software Development: a Systematic Literature Review, PROFES 2018, 19th Int. Conf. on Product-Focused Software Process Improvement, Nov. 28 – 30, Wolfsburg, Germany Soreangsey Kiv, Samedi Heng, Manuel Kolp and Yves Wautelet

1. Agile Manifesto and Practices Selection for Tailoring Software Development: a Systematic
Literature Review
Soreangsey Kiv(1), Samedi Heng(2), Manuel Kolp(1) and Yves Wautelet(3)
(1) UCLouvain LouRIM/CEMIS
(2) HEC Liège, Université de Liège
(3) KU Leuven
International Conference on Product-Focused Software Process Improvement
November 28 – 30, Wolfsburg, Germany

2.  Introduction
 Research Methodology
 Result
 Conclusion & Future Work
2
Content

3.  In 2001, the leaders of eXtreme Proramming (XP), Feature-Driven Development (FDD), Dynamic
Systems Development Method (DSDM), Crystal family and Scrum met and discussed about Agile
methods.
 Agile Manifesto: 4 Values, 12 Principles
3
Introduction: Context
 Many other methods were proposed in respecting of
Agile Manifesto.
Understanding Agile Manifesto
= understanding the core ideas/features of all the
agile methods.

4. ! We have observed that the Agile Manifesto has lost its attention from agile practitioners
! Dave Thomas, Andrew Hunt and Kent Beck, the Agile Manifesto authors raised that “Agile is Dead”
! Moreover, the relations between Agile Manifesto and practices were made based on the
assumption
1. If it is true that Agile Manifesto has been neglected?
2. If Agile Manifesto is important for the development team?
4
Introduction: Problematic

5. A well-defined systematic literature review on the existing case studies of agile methods adoption.
 Verify the point of view of agile practitioners on Agile Manifesto
 Verify the relation between the Agile Manifesto (4 values and 12 principles) and agile
practices, in tailored agile methods adoption.
5
Introduction: Proposition

6. 6
Research Methodology: Research Protocol

7. RQ1: How has the Agile Manifesto and its importance been discussed in tailored agile
methods adoption?
 To verify whether or not the Agile Manifesto has lost its attention.
? RQ1.1: How often has the Agile Manifesto been discussed by agile practitioners during their adoption?
? RQ1.2: In which manner has the Agile Manifesto been discussed, as a whole or only part of it, just as a reminder or
in detail?
? RQ1.3: Has the Agile Manifesto been recognized as important by practitioners for their adoption or not? If it has,
how has it been described?
7
Research Methodology: Research Questions

8. RQ2: Is the Agile Manifesto related to agile practices selection?
 To verify whether or not there is any relation between the Agile Manifesto and practices.
? RQ2.1: Is the Agile Manifesto relevant to the team’s problems that led to tailored agile methods
adoption?
? RQ2.2: Is the Agile Manifesto relevant to the team’s expectations from tailored agile methods
adoption?
? RQ2.3: Is the Agile Manifesto relevant to the team’s benefits of tailored agile methods adoption?
Problem, Expectation and Benefit can be seen as the goals for adopting agile methods.
8
Research Methodology: Research Questions

9.  Search Terms: “(Agile OR Scrum OR XP OR Kanban OR ScrumBan OR Lean OR DSDM OR AgileUP OR
FDD OR Iterative Development) AND ((practice AND select) OR tailor OR customize OR partial OR adopt
OR goal)”
 Search Engines: only consider papers that were published from the year 2000 in peer-reviewed
conferences and journals found in: IEEEXplorer, ScienceDirect, SpringerLink and ACM Digital Library.
9
Research Methodology: Search Strategy

10. Abstract-based Selection Criteria
10
Research Methodology: Study Selection

11. 11
Research Methodology: Study Selection
Full-text-based Selection Criteria
- Describes the influence of agile value or principle over agile methods or practice selection
- Describes how they adopt some set of practices or methods based on their problems or expectations
- Describes the benefits they gained from adopting some set of agile practices or agile methods
As long as one of the criteria is found, the article is included.

12. 12
Research Methodology: Study Selection

13.  Conference/journal name and year of publication
 Type of agile
 Type of institution
 Mention about Agile Manifesto
 Agile Manifesto influence on partial agile adoption
 Problem
 Expectation
 Benefit
13
Research Methodology: Data Extraction
General Information
RQ1
RQ2

14. 14
Result: General Information

15. 15
Result: Research Question 1
RQ1: How has the Agile Manifesto and its importance been discussed in tailored agile methods adoption?
26/51
or 51%
25/51
or 49%
Mention about Agile
Manifesto
Mention about Agile Manifesto
Mention nothing related to Agile
Manifesto
12/26 or
46%
3/26
or
12%
11/26 or
42%
Mention about influence of Agile Manifesto
Do not mention about importance
Simple said that it has influence
Explain its importance in detail
10/26 or
38%
10/26 or
38%
3/26 or
12%
3/26
or
12%
Simply use the word Agile Manifesto
Mention only values
Mention only principles
Mention both values and principle
Different ways mentioning Agile Manifesto

16. 16
Result: Research Question 1
RQ1: How has the Agile Manifesto and its importance been discussed in tailored agile methods adoption?
14/51 or 27%
37/51 or 73%
Acknowledge its
importance
Mention nothing
about its importance
Acknowledge the influence of Agile Manifesto on practices selection

17. 17
Result: Research Question 2
 Answering to RQ2, our intuition was to compare the problems, expectations and benefits extracted from
the 51 selected papers with the Agile Manifesto, i.e., the 4 values and 12 principles
 The mapping process was carried out manually by one author and double checked by another, in the form
of a Cartesian product.
A
B
C
D
E
F
G
A
C
F
A
D
E
F
G

18. 18
Result: Research Question 2
List of Problems
- complex documentation
- lack of communication
- misunderstands and competition between areas
- heroic efforts
- not sustainable
- substantial requirement churn
- too large amount of work in progress
- changing technology and architecture
- code differ from design
- complex and difficult rollbacks
- delayed end-user testing
- delivery pains
- many features are developed that have no business value and are never used by the customers
- require a continuous development
- …

19. 19
Result: Research Question 2
Principle Problem
P2: The most efficient and effective method of conveying information to
and within a development team is face-to-face conversation.
- complex documentation
- lack of communication
- misunderstands and competition between areas
P3: Agile processes promote sustainable development. The sponsors,
developers, and users should be able to maintain a constant pace
indefinitely.
- heroic efforts
- not sustainable
- substantial requirement churn
- too large amount of work in progress
P4: The best architectures, requirements, and designs emerge from
self-organizing teams
- changing technology and architecture
- code differ from design
- complex and difficult rollbacks
P5: At regular intervals, the team reflects on how to become more
effective, then tunes and adjusts its behavior accordingly.
P6: Our highest priority is to satisfy the customer through early and
continuous delivery of valuable software.
- delayed end-user testing
- delivery pains
- many features are developed that have no business value and are
never used by the customers
- require a continuous development

20. 20
Result: Research Question 2
Value Principle
Value1: Individuals and interactions over processes and tools
P1: Build projects around motivated individuals. Give them the environment and
support they need, and trust them to get the job done.
P2: The most efficient and effective method of conveying information to and within a
development team is face-to-face conversation.
P3: Agile processes promote sustainable development. The sponsors, developers,
and users should be able to maintain a constant pace indefinitely.
P4: The best architectures, requirements, and designs emerge from self-organizing
teams
P5: At regular intervals, the team reflects on how to become more effective, then
tunes and adjusts its behavior accordingly.
Value2: Working software over comprehensive documentation
P6: Our highest priority is to satisfy the customer through early and continuous
delivery of valuable software.
P7: Deliver working software frequently, from a couple of weeks to a couple of
months, with a preference to the shorter timescale
P8: Working software is the primary measure of progress.
P9: Simplicity is the art of maximizing the amount of work not done is essential.
Value3: Customer collaboration over contract negotiation
P10: Business people and developers must work together daily throughout the
project.
Value4: Responding to change over following a plan
P11: Welcome changing requirements, even late in development.
P12: Continuous attention to technical excellence and good design enhances agility.

21. 21
Result: Research Question 2
Value Principle
Value1: Individuals and interactions over processes and tools
P1: Build projects around motivated individuals. Give them the
environment and support they need, and trust them to get the job
done.
P2: The most efficient and effective method of conveying
information to and within a development team is face-to-face
conversation.
P3: Agile processes promote sustainable development. The
sponsors, developers, and users should be able to maintain a
constant pace indefinitely.
P4: The best architectures, requirements, and designs emerge
from self-organizing teams
P5: At regular intervals, the team reflects on how to become
more effective, then tunes and adjusts its behavior accordingly.

22. 22
Result: Research Question 2
0
2
4
6
8
10
12
Mapping 42 Problems to Principles
0
2
4
6
8
10
12
14
16
18
V1 V2 V3 V4 Unfound
Mapping 42 Problems to Values

23. 23
Result: Research Question 2
0
5
10
15
20
25
30
35
40
45
Mapping 155 Expectations to Principles
0
10
20
30
40
50
60
70
V1 V2 V3 V4 Unfound
Mapping 155 Expectations to Values

24. 24
Result: Research Question 2
Mapping 205 Benefits to Principles Mapping 205 Benefits to Values
0
10
20
30
40
50
60
70
0
10
20
30
40
50
60
70
80
V1 V2 V3 V4 Unfound

25. 25
Result: Research Question 2
40 out of
42 or
95.24% of
problems
2 out of
42 or
4.76% of
problems
Mapped to at least one principle
Unfound
125 out of
155 or
80.65% of
expectati
ons
30 out of
155 or
19.35% of
expectatio
ns
Mapped to at least one principle
Unfound
Problems Expectations
188 out of
205 or
91.7% of
benefits
17 out of
205 or
8.3% of
benefits
Mapped to at least one principle
Unfound
Benefits

26.  RQ1: Our observation is true, the Agile Manifesto has really lost attention from the development team.
• Among 51 papers, only about half of them 26 mentioned the Agile Manifesto while only 14 acknowledge its
influence.
 In contrary, the results of RQ2 show that Agile Manifesto is highly relevant to team’s problems,
expectations and benefits.
• 95% of problems, 80% of expectations and 92% of benefits can be mapped to the Agile Manifesto
 Agile Manifesto still covers fundamental aspects of any agile method and it is importance for the
teams to understand the Agile Manifesto before adopting any agile method especially a tailored one.
26
Conclusion & Future Work

27.  This study provides a validation on the relation between the Agile Manifesto and agile practices  no more
assumption
 Make the importance of the Agile Manifesto more appealing and evidential
 Create a more complete framework for tailored agile methods adoption in an alternative perspective.
 Agile Manifesto can be regarded as goals that the development team want to achieve or the guideline to
tailor any agile method, to maximize the team’s expectation and eventually the benefits.
 For the next step, build a evidence-based repository to gather the relationships between the Agile
Manifesto and each practice.
27
Conclusion & Future Work