scholarly journals Systematic mapping on the agility evaluation in software development organizations

2019 ◽  
Vol 16 (1) ◽  
pp. 64-76
Author(s):  
Wilson Alfredo Ortega-Ordóñez ◽  
César Jesús Pardo-Calvache ◽  
Francisco José Pino-Correa

Agile software development approaches provide great benefits for organizations; however, their implementation is subject to many challenges. For organizations is important to know the level of agility achieved and the gaps in their transformation process in order to implement improvements in their processes and take advantage of the agile approaches. Keeping this in mind, this article presents a systematic mapping of the literature about the evaluation of agility in software development organizations. As a result, 18 studies were found, which were analyzed and compared taking into account the type of study, the relationship of the evaluation with the principles and agile values, the defined evaluation criteria, the validation methods used, and the proposed tools. In addition, the factors that influence the assessment of agility and the aspects that motivate the interest in this research stream are exposed.

Author(s):  
Torstein Nicolaysen ◽  
Richard Sassoon ◽  
Maria B. Line ◽  
Martin Gilje Jaatun

In this article, the authors contrast the results of a series of interviews with agile software development organizations with a case study of a distributed agile development effort, focusing on how information security is taken care of in an agile context. The interviews indicate that small and medium-sized agile software development organizations do not use any particular methodology to achieve security goals, even when their software is web-facing and potential targets of attack. This case study confirms that even in cases where security is an articulated requirement, and where security design is fed as input to the implementation team, there is no guarantee that the end result meets the security objectives. The authors contend that security must be built as an intrinsic software property and emphasize the need for security awareness throughout the whole software development lifecycle. This paper suggests two extensions to agile methodologies that may contribute to ensuring focus on security during the complete lifecycle.


2020 ◽  
Vol 25 (2) ◽  
pp. 105-116
Author(s):  
Oksana Ņikiforova ◽  
Kristaps Babris ◽  
Jānis Kristapsons

AbstractSoftware development method, which does not have any faults or gaps in project implementation, has not been elaborated so far. Due to this reason, the authors have decided to perform this study to make it easier for the companies, which use one of the agile development methods, to better foresee potential risks and to deal with their consequences. The aim of the research is to identify and classify risks in agile software development methods and the related projects based on the obtained survey data. To achieve the goal, the authors have developed evaluation criteria, as well as implemented practical questionnaire in various software development companies. From the obtained survey data, the risks are classified according to various factors, i.e., the changing highest and lowest priorities and needs in various projects. Thus, the obtained research results can be applied in various areas of project development, changing the order of priority factors.


2021 ◽  
Author(s):  
Nour elhouda Farih ◽  
Khalid Nafil ◽  
Rochdi El Messousi

Context: Estimating effort has always been considered an important element at the start of each software development project. The challenge of estimating the effort of software development lies in its precision. With the emergence of agile methodologies, methods for effort estimation (EE) had to adapt to this new development path. In this article, we are conducting a systematic mapping study on effort estimation in the context of agile software development. Objective: we want to identify the estimation approaches and techniques used in the context of agile development to better understand the specifics and trends relating to this mode of development. Method: we conducted a systematic mapping study by adopting the guideline explained in[1] [2]. A systematic review of the literature [3] has already been carried out for publications between 2001 and 2013. This work is an extension of this previous study. We queried 5 electronic databases. Conclusion: We retrieved 11350 paper from five electronic databases. A total of 108 papers is selected after applying the inclusion and exclusion criteria. Based on the results, there is a general increase over the years of studies concerning effort estimation in agile software development.


Author(s):  
John McAvoy ◽  
Tom Butler

Agile software development (ASD) is now widely used in the software development industry; accordingly, it has been the focus of research with studies featuring in a variety of journals—notable examples are special issues of IEEE Computer (Volume 36, Issue 6) and IEEE Software (Volume 20, Issue 3). The decision by organisations and project teams to adopt an agile methodology is of particular interest to researchers, with the main aim of such studies being to produce a tool or system to assist in that decision. Examples of this research stream are to be found in research by Boehm and Turner (2003, 2004), McAvoy and Sammon (2006), and Pikkarainen and Passoja (2005). Decision making in these treats it as occurring over a short time frame, ending with a specific decision. In Mintzberg, Raisinghani, and Théorêt (1976), decision making is seen to be bounded by the identification of a need for action and ends with a commitment to take specific action. Despite Mintzberg et al.’s (1976) bounding of decision making, commitment to a particular decision can not be assumed to last. The implementation of a decision is longitudinal— that is, its lifecycle is from the commitment to action through to the completion of the action or actions. Throughout the implementation of a decision, many more related decisions are made: for example, decisions based on such considerations as: Do we continue to adopt? Do we need to alter the original decision? Do we need to reassess the actions decided upon? The decision to adopt a software development methodology aligns more with a longitudinal view of decision making than with conceptualizations of decision making as a once off phenomenon. Robin and Finley (1998) argue that the operationalisation of a decision is more significant than the method adopted to arrive at the initial decision. Thus, it may be deduced that in investigating the adoption of an ASD, there needs be a consideration of decision making beyond that of a single meeting or decision point, and the focus broadened to include the impact of time on how decisions are made and actions taken. It is clear from the studies quoted that over the lifecycle of a decision various factors can impact on outcomes associated with decision taking. For example, the group that makes or applies the decision can have a major impact on resulting outcomes, which can be negative—McGrath (1984) for example, discusses many of the decision-related factors that group interaction can influence.


Sign in / Sign up

Export Citation Format

Share Document