Towards successful agile development process in software outsourcing environment: a systematic literature review

2020 ◽  
Vol 23 (2) ◽  
pp. 141
Author(s):  
Muhammad Azeem Akbar ◽  
Muhammad Kashif Shad ◽  
Fong Woon Lai ◽  
Shahid Hussain
IEEE Access ◽  
2017 ◽  
Vol 5 ◽  
pp. 23589-23612 ◽  
Author(s):  
Sikandar Ali ◽  
Li Hongqi ◽  
Siffat Ullah Khan ◽  
Yang Zhongguo ◽  
Zhu Liping

2021 ◽  
Vol 12 (7) ◽  
pp. 339-349
Author(s):  
A. A. Kodubets ◽  
◽  
I. L. Artemieva ◽  

This article contains a systematic literature review of requirements engineering for software systems. The literature published within last 5 years was included into the review. A research question was defined as requirements development process of large scale software system (with thousands of requirements) and an interaction problem during this process (communication, coordination and control). The problem is caused by the fact that large-scale software system requirements process is a cross-disciplinary task and it involves multiple parties — stakeholders, domain experts, and suppliers with own goals and constrains, and thus, the interaction between them seriously slows down the overall requirements development process than writing the requirements specification itself. The research papers were classified by several research directions: Natural Language Processing for Requirements Engineering (NLP4RE), Requirement Prioritization, Requirements Traceability, Quality of Software Requirements, Non-functional Requirements and Requirements Elicitation. Motivation and intensity of each direction was described. Each direction was structured and represented with the key references. A contribution of each research direction into the research question was analyzed and summarized including potential further steps. It was identified that some researchers had met a part of the described problem in different forms during their researches. At the end, other researches were described additionally in a short overview. To approach the research question further potential direction was described.


IET Software ◽  
2013 ◽  
Vol 7 (5) ◽  
pp. 283-293 ◽  
Author(s):  
Mahmood Niazi ◽  
Naveed Ikram ◽  
Muneera Bano ◽  
Salma Imtiaz ◽  
Siffat Ullah Khan

Information ◽  
2019 ◽  
Vol 10 (10) ◽  
pp. 314
Author(s):  
Jimmy Molina Ríos ◽  
Nieves Pedreira-Souto

The current inclusion of agile methodologies in web-oriented projects has been considered on a large-scale by software developers. However, the benefits and limitations go beyond the comforts that project managers delimit when choosing them. Selecting a methodology involves more than only the associated processes or some documentation. Based on the above, we could define as the main concerns the approach with which we identify the methodology, the needs of the company, the size, and qualities of the project, and especially the characteristics of agile development that they possess. However, there are several difficulties in selecting the most appropriate methodology due to the features in common; Will it be suitable for my project? What challenges will be presented in the process? Will my team understand each stage? Will I be able to deliver software that satisfies the client? Project managers create these questions, which seem manageable but have huge effects. This paper presents a systematic literature review based on the analysis of the approaches of six web development methodologies. The aim of the study is to analyze the approaches presented by relevant methodologies, identifying their common agile characteristics and managing to contrast both its benefits and limitations during a project. As a result, we could itemize five common features, which are presented within the processes; (1) flexibility, (2) constant communication of the workgroup, (3) use of UML, (4) the inclusion of the end-user and (5) some documentation.


2020 ◽  
Vol 1 ◽  
pp. 577-586
Author(s):  
J. Heimicke ◽  
R. Chen ◽  
A. Albers

AbstractMore than 15 years after the publication of the agile manifesto of software development, agile development approaches have also reached the processes of physical product development. Because of the boundary conditions and requirements here, which differ strongly from those of pure software development, these approaches often reach their limits. However, research and practice have quickly recognized that hybrid approaches integrate the strengths of agile and plan-driven development. This paper presents 25 hybrid development approaches that have been identified in a Systematic Literature Review.


Sign in / Sign up

Export Citation Format

Share Document