Abstract
In order to adopt specific agile methods and to accommodate lean principles, many organizations need to tailor their processes. Different frameworks supporting and guiding the agile transition and adoption process exist in the literature. However, there is a demand for specific guidelines on the different circumstances influencing agile adoption. This paper provides a Systematic mapping of the available frameworks, issues and factors affecting a successful agile transition and adoption process. Twenty-eight primary studies have been considered. The results are presented according to the three research questions. Firstly, nine systematic approaches and frameworks for agile transition and adoption are analyzed. Secondly, different issues related to the agile transition and adoption process are gathered, compared and synthesized in the following five categories: pre-transformation activities, obstacles and results, stages and activities, agile practices and situational factors. Finally, a list of 154 situational factors affecting the agile transition and adoption process is proposed.
Highlights
Agile methods for software development have been increasingly used in the Information Technology sector [1]–[3]
Section IV.A aims at responding RQ1: Which frameworks for agile transition and adoption exist in the literature? This section presents the identified structured approaches and frameworks for agile transformation process
Sections IV.B, IV.C, IV.D and IV.E aim at responding RQ2: Which issues and aspects are discussed in agile transition and adoption literature and how can they be grouped and organized? Firstly, section IV.B presents activities that may be conducted before the initiation of agile transition and adoption process
Summary
Agile methods for software development have been increasingly used in the Information Technology sector [1]–[3]. After several decades of traditional software development methods, agile methods provided new values to organizations such as fast delivery, customer satisfaction, improved quality, cost of change reduction and decreased documentation [9], [20]. For the Manifesto, a group of experts compared these agile methods and synthesized the basic principles underlying iterative software development. In this regard, four basic values encapsulating the agile methods were derived: individuals and interactions over processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation and responding to change over following a plan [9]. The previously mentioned agile methods are organized around different processes and embed diverse sets of activities and practices, but values defined in the Agile Manifesto represent the backbone of all agile methods
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Free) 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
