Resolving Challenges in Agile Transformation for
Large Scale Development: A Survey
Muhammad Umair Ali Malhi
Department of Computer Science, FAST Lahore
National University of Computer and Emerging Sciences, Pakistan
l165001@lhr.nu.edu.pk
Abstract— Agile methodology is widely being adapted in large
scale software development organizations in different forms like
Scrum and XP in order to gain success in business [1][2][3].
However, as agile was designed primarily for small teams [2]
therefore there are different types of challenges being faced in
adopting this method and as a result companies and teams are
sometimes unable to benefit from this methodology up to its full
potential. This survey paper summarizes current literature
identifying challenges and how they could be addressed in
diverse environments of large-scale software development
organizations.
Keywords— Adopting Agile Frameworks, Large-Scale
Transformation, Challenges of Transformation, Resolutions of
Challenges, Literature Survey
I. INTRODUCTION
Agile methodology has been adopted successfully by lot of
small to medium size software development organizations in
different flavours. Recently, due to its potential benefits, large
organizations are also transforming their software
development model to agile. This methodology helps
organizations in adapting to ever changing needs of
customers and in providing early and frequent delivery of
valuable software products to their customers which are the
main principles behind agile manifesto.
Many organizations are shifting to agile mainly for success
of their business [1]. Another reason for this transformation is
to reduce technical debt by frequent delivery which could
ultimately improve software quality by lesser errors released
in production code [1]. As more and more organizations are
coming towards this process, the types of agile frameworks
and their actual implementations are getting lots of flavours.
This could not be considered unexpected as agile frameworks,
like any other development framework, just provide the
guidelines to perform certain activities. However, as agile
was basically intended for small or single-team projects, its
adaptation by large-scale organizations and teams is more
challenging [2]. Therefore, it needs to be analysed in detail
what are the challenges in using agile and what are could be
the methods that could help in dealing with those challenges
and ultimately result in success of business if agile
methodology is used.
Further as agile methodology is being adopted in different
flavours, it needs to be established at which level of agile
model the organization is currently working at in order to
assess the challenges and ways of improvement. This will
also clarify whether agile is good for large-scale software
development as well or is it only good for small teams as it
was originally designed for [2].
In this survey of literature, we will focus on the following
research questions:
 RQ1: What are the main challenges being faced in agile
transformations for large-scale development?
 RQ2: What are the solutions presented for those
challenges found in agile transformations for large-
scale development?
In order to find out the list of challenges in different phases
of agile software development life cycle for large scale
organizations, we will survey most recent articles and
proceedings of conferences on this topic that covered the
challenges and proposed ways to handle those challenges
faced by large-scale organizations in transformation to agile
methodology by using different techniques in reaching to
their respective conclusion.
The rest of the paper will contain background information
about agile software development, it’s basic principles and
comparative analysis of challenges presented in recent
literature about transforming to agile methodology by large-
scale organizations. In the end, conclusion is provided based
upon analysis of that literature.
II. BACKGROUND AND RELATED WORK
Agile methodology is widely being adapted in software
development organizations in different forms like Scrum and
XP in order to gain success in business [1]. This is not only
true for small software development teams as agile was
originally intended for [2] but also for large scale system
development teams and companies [3].
A. Principles of Agile
Different companies are adopting agile based upon their
experience, culture and their practices which they had been
following in traditional software development before going
for the transformation to agile methodology. However,
following are certain basic principles that could be considered
for adopting agile [4].
 Early and frequent delivery of valuable products.
 Adapting to ever changing requirements.
 Deliver recurrently in shorter time spans.
  Daily communication between business stakeholders
and developers.
 Trust energetic and self-driven individuals to complete
the job on their own.
 Increase face-to-face conversation within teams.
 Measure of progress should be working software.
 Maintain constant pace and promote continuous
development.
 Focus on technical excellence and good design help in
promoting agility.
 Simplicity by prioritizing most valuable features.
 Self-organized teams provide best output.
 Regular self-assessment improves effectiveness and
adjustment in behaviour.
B. Levels of Agile Methodology
Conboy et al. [5] define agility as, also quoted by Dingsøyr
et al. [6], the continuous readiness "to rapidly or inherently
create change, proactively or reactively embrace change, and
learn from change while contributing to perceived customer
value (economy, quality, and simplicity), through its
collective components and relationships with its
environment." As per this definition and principles of agility
mentioned in preceding section different companies are
following their own set of practices to achieve this basic goal.
The practices followed by different companies may differ
in a way that the end result could be different for different
practitioners. Therefore, the companies in their earlier stages
of transformation to agile are mostly unclear about their
methods and do not know for sure if they are doing that right
[1]. In order to understand that position, organizations could
be assed and categorized in different types of models having
multiple levels. For the sake of understanding we can look at
the following five levels, as presented by Laanti [1], based
upon their practices of following agile methodology and
principles.
1) Level-1 Beginner: At this initial level an organization
understands the effectiveness of smaller batches and arrange
its work in backlogs along with new tools and roles to support
agile.
2) Level-2 Novice: Novice level is that in which
organization focuses on more fluent releases with automation
of development and testing flow. Also it starts measuring its
process and flow using agile related metrics.
3) Level-3 Fluent: This level means the organization fully
understands the agile benefits and focuses on improvement in
its learning by collecting more and more related data.
4) Level-4 Advanced: At this level, agile process model
and utilization of data becomes perfect and agility is
considered integral part of company’s values and strategy. All
new development is approached with agile practices in mind
and agility is the driving force.
5) Level-5 World-class: World-class level means the
organization has its own approach to agile practices and no
more growth in its area would be expected.
C. Large Scale Development
In order to understand the challenges in large-scale agile
development, we need to understand the what we mean by
large-scale. In literature, large-scale development for agile
encompasses large-teams, large projects having multiple
teams, and implementation of agile in whole organization [6].
Dingsøyr et al. [6], have summarized different definitions
of large-scale agile development as per participants of
workshop XP2014 and it could be seen that by large-scale
agile development the general concept is dependent upon
number of people involved, size of the project code, number
of locations, and number of teams involved in a development
project. Dingsøyr et al. [6] also considered number of
collaborating and coordinating teams as the criteria for large-
scale agile development. However, these definitions do not
take the agile methods being applied in large organization in
to consideration and could be considered as a different area of
research [6].
Similarly, Paasivaara et al. [7] considered number of teams
and people involved as the criteria for large-scale agile
development while Berger et al. [8] considered the project
cost for this purpose. In their case study, Peterson et al. [9]
considered lines of code for large-scale system. Additional
studies also considered such approach of people, code size,
locations, teams and cost for defining large-scale agile
development.
D. Challenges in Agile Transformation
Review of literature shows that there are different types
challenges present for companies transforming to agile
methodology. The challenges could include management
overhead in team coordination as well as low test coverage
[9]. The challenges in agile transformation increase with
increase in organization size [10]. However, as per Livermore
[11], there is no direct correlation between success of agile
and size of development team but the challenge increase due
to greater effort required in breaking higher internal inertia in
larger organizations. Training and active management
involvement could help in overcoming such challenges [11].
Heikkilä et al. [12] mentioned problems like over-
commitment, insufficient understanding of the development
team autonomy, and growing technical debt which could be
faced in large-scale agile development.
Effective coordination between teams [13] and
collaboration with external experts [14] also become
challenging with self-management principle of agile [13][14].
Working in parallel also becomes challenging in scrum
like environment in case of emerging software architecture as
it could cause delays due to dependencies in large-scale agile
development [15].
Large organizations and large-scale development contain
multiple teams which are dependent upon each other. This
introduces the challenge of keeping balance between formal
documentation and following agile principles [16].
III. RESEARCH METHODOLOGY
Review of literature is also a way to of identify, evaluate
and interpret the research which is related to a specific area of
interest, topic, or research question. This is suitable for
providing summarized results from existing literature, for
understanding difference between the existing research, as
well as identifying open areas to provide basis of new
research.
In this paper, we will survey the most recent literature from
well-known journals on the topic of managing challenges in
agile transformations for large-scale development. The
review is primarily based upon the literature published in the
field of software engineering.
Different topics and areas could be selected against agile
transformations in large-scale development, however, as agile
was mainly presented for small teams, there are more chances
of facing challenges in large-scale organizations and hence
the need to resolve those challenges as per known practices
and studies. Hence, the research questions presented are quite
related to each other and review of appropriate literature from
similar viewpoints could present the multiple solutions to
single problem.
TABLE I
SELECTION OF PAPERS
Selection criteria for Relevant Literature
Criteria Related Non-related
Agile Organization is Practicing agile for
Transformation adopting Agile long time
Large-scale More people and Just large setup but
Development teams involved less involved
Challenges for Challenges faced Challenges in
Agile against agile development
Most Recent Within current and Anything published
previous year before 2016
The research area presented and questions of the research,
helped us in defining the criteria for including or excluding a
certain article in our review: agile transformation, large-scale
development, challenges in agile and being more recent.
Table I lists the criteria and offers a little explanation on
related and non-related topics. We considered the articles
which fulfilled all these criteria.
Considering the above mentioned criteria we short-listed
ten different articles covering our research questions from
different viewpoints. Following is the brief overview of those
articles selected for review.
First of that list is systematic literature review by Dikert et
al. [2], which covers the challenges and presents success
factors for agile transformation by systematically reviewing
the literature up to that time (2016). It is included because it
will give the insight of most of the related literature
presenting challenges of agile transformation in large-scale
software development.
Heikkilä et al. [12] presented the ways to manage the
challenges related to requirements flow in adopting agile by
large-scale organizations. Their study was comprised of node
development in Ericsson telecommunications and focused on
how the requirements flow from strategy to release, and what
are the problems and benefits of using agile.
Hohl et al. [17] described the challenges faced by adopting
agile in large-scale software development linked with
automotive domain. They also discussed challenges faced due
to particular characteristics of the automotive field such as
requirements that demand high quality and large number of
interfaces linked with fixed and defined processes.
Adams [18] provided a unique viewpoint of challenges
which could be faced by software development adopting agile
methodology in government and bureaucratic sector. The key
areas revealed in that study that presented challenges are
acquisition oversight, contracting, cost estimation,
information assurance, program cost, performance monitoring,
culture, and requirements management.
Kasauli et al. [19] discussed possible scopes of applying
agile in large-scale development along with importance of
requirements and challenges that could be faced in large-scale
agile system development. Their case study was based upon
four different companies including one telecommunication,
two automotive and one embedded systems software
development company. The diverse nature of companies will
help us in generalizing the results and give better
understanding of challenges faced in agile.
Almeida [20] presented challenges in four different
dimensions which could be faced by companies in shifting
from waterfall to agile software development methodology.
The systematic literature review included thirteen different
studies relevant to the topic and summarized the practices that
could be applied to manage and mitigate challenges faced
during transformation to agile.
Türpe et al. [21] highlighted the requirement of integrating
security related activities in agile development process
specifically focusing on Scrum. They presented the tensions
and challenges that could arise due to optimization of Scrum
to explicit requirements and proposed the need of special
focus required for implicit security needs, the estimation and
arrangement of security related tasks and to improve
collaboration, verification and feedback mechanism for
security.
Neto et al. [22] presented new challenges that may arise in
requirements engineering and system testing due to adoption
of agile in large-scale software development. Their case study
focused on collecting and elaborating challenges that
companies face in requirements engineering while
transforming to agile in large-scale development. They
interviewed focused group by conducting workshops in three
different companies including telecommunication, package
manufacturing and automotive.
Obrutsky et al. [23] investigated the most common
challenges faced by project management due to adoption of
agile methodology on large-scale by software development
organizations. They used the review of literature and survey
based approach for finding out the barriers and pointed out
direction or possible ways to overcome those barriers.
Ahmed et al. [24] analysed the challenges to management
of knowledge in agile based global kind of software
development. They reviewed the literature to identify those
barriers and presented ways to prioritize them in order to
effectively overcome those barriers while successfully
implementing agile methodology in global software
development.
IV. DISCUSSIONS AND IMPLICATIONS
In this section we will analyse the most important
challenges presented in respective articles specifically related
to agile transformation for large-scale software development.
For that we will divide these challenges in following areas
and sub-areas for better understanding:
A. Organizational Management
In order to successfully implement a process in an
organization, higher management plays a vital role.
Following are some common challenges discussed in the
reviewed articles that relate to management of an
organization:
1) Resistance to Change: The most important issue in
transformation is the resistance that could be faced at
every level of the organization to adopt agile practices.
There could be different reasons for resisting to
change like avoiding risks of new areas [2][20], fear of
new responsibilities [2][20], use of good existing
processes [17][19], lack of business and process
knowledge [2][12][17][19][20] and misunderstanding
[19]. In order to overcome these challenges, it is
important to make support from management visible
to employees and ensure it at all levels [2]. It is
important to educate management as well as
employees on the concept of agile [2][19][20]. It is
also necessary to involve customers in the new roles
for agile and continuously improve the agile
understanding [19].
2) Management living in old times: It has been observed
that during or even after transitioning to agile
methodology, the expectations and demands of
management remain the same as per previous process.
For example, management expected up-front long-
term plans and meetings similar to rigid waterfall like
approach which is against the principles of agile
[2][12]. This rigidity to waterfall like approach in
controlling the development processes is one of the
key hurdles to adoption of agile [2][23]. In order to
overcome this challenge, it is suggested to make the
transition gradual and volunteer [23].
3) Internal Silos: Internal divisions within an
organization also hinders the implementation of agile
by reducing commination, promoting difference in
priorities and agendas in different teams [2][20][23].
Conforming to single approach across whole
organization should be encouraged to overcome this
barrier [2]. Also sharing knowledge among teams
[22][24] is also important to reduced different in
priorities which could arise if teams are working in
isolation.
4) Lack of Agile Understanding: It has also been
observed that lack of understanding of agile practices
causes issues in conforming to agile standards and
getting benefits from agile [2][23]. Also the
universities are choosing curriculum based mainly
upon traditional development due to which newly
hired employees lack knowledge about agile [12]. In
order to cope with this challenge, it is necessary to
have people with agile experience [23] or train
employees across the organization to give them proper
understanding of agile and how to implement it
[2][12].
B. Requirements Engineering
Adapting to ever changing needs and lesser documentation
principles of agile introduce new challenges in the phase of
requirements engineering which are not so common in other
phases of software development. Following are some
challenges which are presented in literature under review.
1) Defining Requirements: It has been observed that
clearly defined requirements in the form of user stories
which could easily be verified and updated to provide
value to customer is one of the biggest challenge in
transformation to agile [2][18][19][20][22]. Reasons
could be giving requirements to development team
which are too high level [2], evolving requirements
which are difficult to prioritize [18], dividing large
user stories which give customer value so that they
could be delivered in sprint [19][22], and missing
requirements due to low customer involvement [20].
Solution lies in training of employees and teaching
skills so that high level requirements could be broken
down to meaningful user stories [2], updating contract
strategy to involve customers, increase user interaction
and reduce hurdles [18][20]. Also there is need to
follow the agile practices to help in accommodating
change in requirements [22].
2) Managing Change in Requirements: The foremost
principle of agile is to adapt to change in requirement
even in later stages. However, that becomes difficult
in large-scale development when the development
teams are focused on short-term goals and not looking
at the big picture [12]. For this case any change at the
later stages of development could be very difficult to
accept if the structure of software is not flexible
enough [2][18][19][22]. In order to overcome this
challenge, it is necessary to follow agile practices of
requirements management, planning continuously and
provide the understanding of requirements to all
related teams, by increasing communication to cater
for lesser amount of documentation in agile [19][22].
 3) Levels of Abstraction: Large-scale software
development presents a challenge due to different
level of requirements being managed from high-level
customer to individual unit-level viewpoints
[2][12][22]. This is especially true in cases where
complexity of the product demands multiple layers of
project management, and for this case requirements
are drafted and refined by different levels of
stakeholders from customers to development team
members [2]. As it is not possible for all the
stakeholders to communicate with each other due to
management levels or distribution [2], it becomes a
challenge to decompose requirements [22] accurately
from higher level of abstraction to concrete lower
level. This may also result in loss of important
knowledge due to decomposition or provision of all
information in bulk [19]. In order to overcome these
challenges, role of Product Owner (PO) should be
emphasized [2] and also necessary training of skills
could be provided to refine the requirements or
systematic approach could be adopted to communicate
requirements down to the development teams [19][22].
C. Testing for Functional Requirements
Informal communication/coordination and lesser
documentation in agile software development methodology
presents a risk of losing important knowledge related to a
specific project. This loss impacts testing of the software
components as well due to insufficient information available
to testing teams.
1) Insufficient Test Cases: It has been commonly
observed that in order to reduce the documentation, the
agile community uses testing artefacts as a substitute
for requirements specifications [19]. This approach
however useful, results in loss of important
information containing the rationale of a specific
requirement. In order to handle this issue, it is
important to manage the requirements separately from
test-cases and base the test-cases upon those
requirements instead of following test-driven
development [19][22].
2) Ambiguity in Requirements: Ambiguity in
requirements has a great impact on testing of software.
In traditional development, most of the ambiguity gets
clear during long development phase and as testing
comes at the end of the cycle, this challenge is not
faced up to the extent which is common for agile based
large-scale software development [2]. Clearly defined
requirements and updating test-cases is the obvious
way to handle this challenge however, in order to do so,
it is necessary to train the team about agile way of
managing requirements [2][12].
3) Maintaining link with Requirements: It has also been
observed that creating link of test-cases with system
requirements and maintaining that link over-time due
to changes in requirements has become difficult and
costly [22]. Also as user stories define the
implementation of a totally different new feature and
may not be linked to a requirement already defined and
being implemented it becomes difficult to maintain a
trace and link it to specific test cases [19]. It was seen
that tools were available to create and maintain that
link but due to lack of understanding the use of tools as
per agile process was not adopted [22]. In order to
handle this issue there is need to continuously plan and
arrange frequent meetings to analyse and bridge the
gap as team will provide their status in each review
meeting [22].
D. Testing for Quality Requirements
In order to completely test a large-scale system, it is
necessary to accommodate testing of non-functional and
quality requirements like performance, security, and load
testing [2][21][22]. These type of quality related requirements
do not usually come up in user stories [2] or some quality
issues like security may arise due to agile way of
development when bigger picture is not visible and
development process may introduce certain vulnerabilities
[21]. In order to handle this issue in non-functional quality
requirements it is necessary to define them in backlog items
or handle them as requirement [21]. However, not all these
type of requirements could be handled in same way as some
requirements like load and security testing would need special
expertise or external consultancy in terms of team as well as
organization may be required [21] which would need special
modification to agile practices to maintain team autonomy
effectively.
V. CONCLUSIONS
In this paper, we reviewed the most recent literature
presenting challenges and ways to overcome them in
practicing agile for large-scale software development. We
analyzed 10 papers taking different approaches including case
studies, literature review, surveys, focused group interviews
to find out challenges and their resolutions for large-scale
agile transformations.
These studies mainly focused on requirements related
challenges and organizational issues which may hinder the
agile practices in large-scale development. Looking at these
challenges and the amount of literature published so much
recently suggests that despite vast number of software
development shifting to agile, there is still lack of proper
adoption of agile in large-scale development sector. The most
common challenges mentioned in this recent literature are
difficulty to implement agile, delivering implicit requirements,
resistance to change, and challenges related to requirement
engineering.
The most common solutions presented to overcome these
challenges are following agile methodology to its full extent
after customizing to organizational needs, support from
management by changing their demands as per agile process,
alignment of roles and expectations to agile methodology,
along with proper coaching and training of employees as well
as educating the customer of agile specific needs and
expectations.
For future research, we can suggest surveys and case
studies on adopting agile practices and the challenges in
implementing implicit requirements for large scale software
development and studies on defining agile frameworks
generic to most of the large-scale software development
organizations.
ACKNOWLEDGMENT
I would like to thank Dr. Kashif Zafar for his guidance and
motivation to write this survey and Department of Computer
Science, FAST, NUCES for their support and help in
accomplishing this task.
REFERENCES
[1] Maarit Laanti, “Agile Transformation Model for Large Software
Development Organizations,” in Proc. of the XP2017 Scientific
Workshops, paper 19, p. 19:1-19:5, ACM, 2017.
[2] Kim Dikert, Maria Paasivaara, Casper Lassenius, “Challenges and
success factors for large-scale agile transformations: A systematic
literature review,” In Journal of Systems and Software, vol. 119,
Elsevier, 2016.
[3] O. Salo and P. Abrahamsson, "Agile methods in European embedded
software development organisations: a survey on the actual use and
usefulness of Extreme Programming and Scrum," in IET Software, vol.
2, no. 1, pp. 58-64, February 2008.
[4] K. Beck, A. Cockburn, R. Jeffries, and J. Highsmith, (2001)
"Principles behind the Agile Manifesto". [Online]. Available:
http://agilemanifesto.org/principles.html, Accessed On: 2017-11-29.
[5] K. Conboy, "Agility from First Principles: Reconstructing the Concept
of Agility in Information Systems Development," in Information
Systems Research, vol. 20, pp. 329-354, 2009.
[6] T. Dingsøyr, N.B. Moe, “Towards Principles of Large-Scale Agile
Development”. in Dingsøyr T., Moe N.B., Tonelli R., Counsell S.,
Gencel C., Petersen K. (eds), “Agile Methods. Large-Scale
Development, Refactoring, Testing, and Estimation. XP 2014”.
Lecture Notes in Business Information Processing, vol. 199. Springer,
Cham, 2014.
[7] M. Paasivaara, B. Behm, Lassenius, C., Hallikainen, M., 2014.
"Towards rapid re- leases in large-scale xaas development at ericsson:
A case study". in Global Soft- ware Engineering (ICGSE), IEEE 9th
International Conference, pp. 16–25, 2014.
[8] H. Berger, P. Beynon-Davies, “The utility of rapid application
development in large-scale, complex projects”, in Information Systems
Journal, pp. 549-570, 2009.
[9] K. Petersen, C. Wohlin, "The effect of moving from a plan-driven to
an incremental software development approach with agile practices,"
in Empirical Software Engineering, Volume 15, Issue 6, pp 654–693,
Springer, 2010.
[10] T. Dybå, T. Dingsøyr, "Empirical studies of agile software
development: A systematic review," in Information and Software
Technology, vol. 50, issue 9-10, pp. 833-859, Aug. 2008.
[11] J.A. Livermore., "Factors that Significantly Impact the
Implementation of an Agile Software Development Methodology," in
Journal of Software, vol. 3, issue 4, pp. 31–36, Apr. 2008.
[12] V. T. Heikkilä, M. Paasivaara, C. Lasssenius, D. Damian, C. Engblom,
"Managing the requirements flow from strategy to release in large-
scale agile development: a case study at Ericsson," in Empirical
Software Engineering, vol. 22, issue 6, pp. 2892–2936, Jan. 2017.
[13] J. A. Ingvaldsen and M. Rolfsen, "Autonomous work groups and the
challenge of inter-group coordination," Human Relations, vol. 65, pp.
861-881, Jul 2012.
[14] N. B. Moe, D. Smite, A. Sablis, A.-L. Börjesson, and P. Andréasson,
"Networking in a large-scale distributed agile project," presented at the
Proceedings of the 8th ACM/IEEE International Symposium on
Empirical Software Engineering and Measurement, Torino, Italy, 2014.
[15] M. Paasivaara, C. Lassenius, and V. T. Heikkila, "Inter-team
Coordination in Large-Scale Globally Distributed Scrum: Do Scrum-
of-Scrums Really Work?" Proceedings of the ACM-IEEE
International Symposium on Empirical Software Engineering and
Measurement (ESEM'12), pp. 235-238, 2012.
[16] M. Lindvall, D. Muthig, A. Dagnino, C. Wallin, M. Stupperich, D.
Kiefer, J. May, T. Kahkonen, "Agile software development in large
organizations," in Computer, vol. 37, no. 12, pp. 26-34, Dec. 2004.
[17] P. Hohl, J. Münch, K. Schneider, M. Stupperich, "Real-Life
Challenges on Agile Software Product Lines in Automotive," in
International Conference on Product-Focused Software Process
Improvement, PROFES 2017, pp. 28-36, Springer, Oct. 2017.
[18] L. Adams, "Agile Software Development in the Department of
Defense Environment," in Defense Acquisition University, Aberdeen
Proving Ground United States, 2017.
[19] R. Kasauli, G. Liebel, E. Knauss, S. Gopakumar and B. Kanagwa,
"Requirements Engineering Challenges in Large-Scale Agile System
Development," in IEEE 25th International Requirements Engineering
Conference (RE), Lisbon, pp. 352-361, 2017.
[20] F. Almeida, "Challenges in Migration from Waterfall to Agile
Environments," in World Journal of Computer Application and
Technology, vol. 5, pp. 39-49, 2017.
[21] S. Türpe, A. Poller, "Managing security work in scrum: Tensions and
challenges," in International Workshop on Secure Software
Engineering in DevOps and Agile Development (SecSE), vol. 1977,
pp.34-49, Sep. 2017.
[22] F. G. d. O. Neto, J. Horkoff, E. Knauss, R. Kasauli and G. Liebel,
"Challenges of Aligning Requirements Engineering and System
Testing in Large-Scale Agile: A Multiple Case Study," in IEEE 25th
International Requirements Engineering Conference Workshops
(REW), Lisbon, pp. 315-322, 2017.
[23] S. Obrutsky, E. Erturk, "The Agile Transition in Software
Development Companies: The Most Common Barriers and How to
Overcome Them," in Business and Management Research, Sciedu
Press, vol. 6, no. 4, Nov. 2017.
[24] Z. Ahmed, Z. Mansor, K. Ahmad, "An Analysis of Knowledge
Management Challenges in Agile Global Software Development," in
Journal of Telecommunication, Electronic and Computer Engineering
(JTEC), vol. 9, no. 3-4, 2017.
[25] Add after 2nd last.