Abstract
Software development methodologies are constantly evolving due to the appearance of new technologies and increasingly demanding user requests. Organizations seek to respond to these new challenges by changing their work practices, both at the technical and organizational levels. Agile methodologies thus emerge as a new development model characterized by greater flexibility and responsiveness to these new requirements, but also introduced new challenges. This study adopts a systematic review methodology to identify the key challenges in the migration process from traditional software development paradigms to agile methodologies. Four dimensions of challenges and a total of 49 sub-dimensions were found. Additionally, we discussed how those challenges can emerge, and what practices can be applied to properly manage and mitigate them.
Highlights
Software has become larger, more complex, and demands high quality standards, because it occupies a prominent place within organizations, and not infrequently, is an essential part of the business
Several models of so-called agile methods have been created, all focused on de-bureaucratizing the activities associated with software production
Among the most used agile methodologies are SCRUM, XP, TDD, Agile Unified Process, among others. Each of these methods is usually a specialist in some software engineering practices, and when an organization wants to adopt the agile ecosystem, the correct approach is to implement a set of methods so that its entire development process can benefit from those practices
Summary
More complex, and demands high quality standards, because it occupies a prominent place within organizations, and not infrequently, is an essential part of the business. In addition to these factors, the dynamics of the business market and the constant emergence of new technologies, make their projects extremely dynamic and with short deadlines. Among the most used agile methodologies are SCRUM, XP, TDD, Agile Unified Process, among others Each of these methods is usually a specialist in some software engineering practices, and when an organization wants to adopt the agile ecosystem, the correct approach is to implement a set of methods so that its entire development process can benefit from those practices
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
