Agility in Software Development and Project Value

2022 ◽  
pp. 356-376
Author(s):  
VenuGopal Balijepally ◽  
Gerald DeHondt ◽  
Vijayan Sugumaran ◽  
Sridhar Nerur
Keyword(s):  
Best Practices ◽  
Software Development ◽  
Survey Data ◽  
Theoretical Perspective ◽  
Agile Development ◽  
Software Teams ◽  
What Works ◽  
The Individual ◽  
Development Methods ◽  
Over Time

Agile Development Methods, considered as an alternative to the traditional plan-based methods, have received much attention since their inception. These practices have evolved and developed over time, culminating in 2001 with the Agile Manifesto. Since that time, preferred methodologies, implementations, and best practices have continued to evolve with a focus on doing what works best for the individual company or project. However, the concept of agility in software development has remained quite nebulous, lacking in clarity particularly about its underlying dimensions. In this research the authors conceive agility in terms of four distinct dimensions. Drawing from the theoretical perspective of holographic organization, they develop a model explaining how each of these underlying dimensions of agility contributes to project value in software teams. The authors test the model using survey data collected from industry practitioners and discuss findings.

Agility in Software Development and Project Value

2017 ◽  
Vol 28 (4) ◽  
pp. 40-59 ◽  
Author(s):  
VenuGopal Balijepally ◽  
Gerald DeHondt ◽  
Vijayan Sugumaran ◽  
Sridhar Nerur
Keyword(s):  
Best Practices ◽  
Software Development ◽  
Survey Data ◽  
Theoretical Perspective ◽  
Agile Development ◽  
Software Teams ◽  
What Works ◽  
The Individual ◽  
Development Methods ◽  
Over Time

Agile Development Methods, considered as an alternative to the traditional plan-based methods, have received much attention since their inception. These practices have evolved and developed over time, culminating in 2001 with the Agile Manifesto. Since that time, preferred methodologies, implementations, and best practices have continued to evolve with a focus on doing what works best for the individual company or project. However, the concept of agility in software development has remained quite nebulous, lacking in clarity particularly about its underlying dimensions. In this research the authors conceive agility in terms of four distinct dimensions. Drawing from the theoretical perspective of holographic organization, they develop a model explaining how each of these underlying dimensions of agility contributes to project value in software teams. The authors test the model using survey data collected from industry practitioners and discuss findings.

scholarly journals Survey on Risk Classification in Agile Software Development Projects in Latvia

2020 ◽  
Vol 25 (2) ◽  
pp. 105-116
Author(s):  
Oksana Ņikiforova ◽  
Kristaps Babris ◽  
Jānis Kristapsons
Keyword(s):  
Software Development ◽  
Survey Data ◽  
Evaluation Criteria ◽  
Agile Software Development ◽  
Agile Development ◽  
Development Projects ◽  
Development Method ◽  
Potential Risks ◽  
Agile Software ◽  
Development Methods

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.

scholarly journals Modelo Aplicable A La Gestión De Procesos Ágiles De Desarrollo De Software Basado En Cmmi –Dev 1.3 Y Scrum

2015 ◽  
Vol 3 (1) ◽  
Author(s):  
Adriana Iglesias ◽  
Acellys Messino ◽  
Patty Pedroza ◽  
Ricardo Llanos
Keyword(s):  
Best Practices ◽  
Software Development ◽  
Continuous Improvement ◽  
Process Management ◽  
Model Development ◽  
Agile Development ◽  
Total Quality ◽  
Model Quality ◽  
Development And Management ◽  
Buenas Prácticas

El presente Artículo de Investigación propone un modelo orientado a las necesidades de calidad total en las organizaciones dedicadas al desarrollo de software conforme a la alineación de los procesos de desarrollo y gestión con los objetivos organizacionales; lo cual hace pertinente la formulación de un modelo de gestión de procesos de desarrollo basado en los principios y prácticas del enfoque ágil, orientado hacia la aplicación de buenas prácticas y procesos de mejora continua. El modelo planteado se denomina SUMM - “Modelo Unificado de Madurez de Scrum” y está orientado a la gestión de procesos ágiles de desarrollo de software enmarcados en las buenas prácticas de CMMI-DEV 1.3 y el marco de trabajo de SCRUM. SUMM consta de cinco niveles de madurez, de acuerdo a la representación por etapas de CMMI - DEV, estos niveles a su vez están compuestos de Metas, Objetivos, Prácticas e Indicadores que permitirán a la organización poder emplear un modelo de desarrollo ágil de calidad, enfocados en procesos de mejora continua.AbstractThis article of Research proposes a model oriented to the needs of total quality in organizations dedicated to software development according to the alignment of development and management processes with organizational objectives, which makes the formulation of relevant management model development process based on the principles and practices of agile approach towards the application of best practices and continuous improvement processes. The proposed model is called SUMM - "Unified Model Scrum Maturity" and is focused on process management software development agile framed in the best practices of CMMI-DEV 1.3 and SCRUM framework. SUMM consists of five maturity levels, according to the staged representation of CMMI - DEV, these levels in turn are composed of Goals, Objectives, Practices and indicators that enable the organization to employ an agile development model quality focused on continuous improvement processes.

scholarly journals Quality of agile adoption in global software development: An assessment model

2021 ◽  
Vol 21 (1) ◽  
pp. 367
Author(s):  
Mahnaz Afshari ◽  
Taghi Javdani Gandomani
Keyword(s):  
Software Development ◽  
Assessment Model ◽  
Global Software Development ◽  
Agile Development ◽  
Related Factors ◽  
Face To Face ◽  
Human Power ◽  
Software Teams ◽  
Research Gap

<span>Over the last decade, software development has faced two approaches to Agile and global software development (GSD). While Agile development is focused on the reduction of software development overhead by reducing the distance between individuals and face-to-face communications, in global software development, the use of human power in various sites is considered. Despite their inherent differences, the combination of these two approaches has received considerable attention from researchers and software professionals. Meanwhile, the lack of a model or tool capable of assessing teams' adaptation to Agile methods seems to be a research gap. The current research aims to solve this challenge by proposing a model in this regard. Considering the major related factors and weighting them, this model allows software teams to assess the rate of their adaptation and success in global software development.</span>

Agile Embedded System Development versus European Space Standards

2017 ◽  
Vol 8 (1) ◽  
pp. 1-23
Author(s):  
Ville Rantala ◽  
Kaisa Könnölä ◽  
Samuli Suomi ◽  
Minna Isomäki ◽  
Teijo Lehtonen
Keyword(s):  
Software Development ◽  
Embedded System ◽  
System Development ◽  
Agile Methods ◽  
Agile Development ◽  
Space Systems ◽  
European Cooperation ◽  
Space Projects ◽  
Mission Critical ◽  
Development Methods

Agile development methods are widely utilized in software development. There is a growing interest and effort to introduce them to other areas of technology, such as development of space systems. Space systems are typically safety- and mission-critical and therefore their development is strongly regulated and standardized. European Cooperation for Space Standardization (ECSS) has created a collection of standards which are extensively followed mainly in European space projects. In this paper, a review and discussion are presented to find out the conflicts between the agile development and the ECSS standards. The presented analysis and discussion show that the ECSS standards do not fully prevent the utilization of agile methods. However, there are aspects to be taken into account in the development methods, contracts and tailoring of standards.

Usability Integration in Agile Development Processes: A Practice-Oriented Best Practice Approach

i-com ◽  
2015 ◽  
Vol 14 (2) ◽  
Author(s):  
Hartmut Schmitt ◽  
Dominik Magin ◽  
Andreas Maier ◽  
Richard Wacker ◽  
Josh Wang
Keyword(s):  
Best Practices ◽  
Software Development ◽  
Best Practice ◽  
Agile Software Development ◽  
Agile Development ◽  
Ministry Of Education ◽  
Team Members ◽  
Ui Design ◽  
Practice Approach ◽  
Agile Software

AbstractSmall and medium-sized enterprises (SMEs) increasingly rely on agile software development. However, the majority of established usability methods have been developed with traditional software engineering principles in mind. So, one might assume that these methods and tools might not be applicable to agile development projects. In this paper, a possible approach to systematically adapting traditional usability methods to application in agile projects is introduced and documented as best practices. These best practices can be quickly and dynamically employed by agile development team members and can thus contribute to higher quality of software development outputs. The approach described in this paper was developed in the context of a German research project funded by the German Federal Ministry of Education and Research (BMBF) and conducted by one research institute and three software-developing enterprises and will be evaluated throughout the further course of the project. For this purpose, a number of best practices have been adapted to the context of agile software development and described in detail in order to allow inexperienced software developers of small and medium-sized enterprises to successfully apply these best practices. As two examples of these best practices, we illustrate the best practices ‘Contextual Inquiry’ and ‘Template-Based UI Design’ in this paper.

scholarly journals Coordinating Knowledge Work in Multiteam Programs

2018 ◽  
Vol 49 (6) ◽  
pp. 64-77 ◽  
Author(s):  
Torgeir Dingsøyr ◽  
Nils Brede Moe ◽  
Eva Amdahl Seim
Keyword(s):  
Software Development ◽  
Large Scale ◽  
Development Program ◽  
Knowledge Work ◽  
Agile Development ◽  
Development Projects ◽  
Development Programs ◽  
Knowledge Based ◽  
Over Time

Software development projects have undergone remarkable changes with the arrival of agile development approaches. Although intended for small, self-managing teams, these approaches are used today for large development programs. A major challenge of such programs is coordinating many teams. This case study describes the coordination of knowledge work in a large-scale agile development program with 12 teams. The findings highlight coordination modes based on feedback, the use of a number of mechanisms, and how coordination practices change over time. The findings can improve the outcomes of large knowledge-based development programs by tailoring coordination practices to needs over time.

scholarly journals Coordination Strategies: Managing Inter-team Coordination Challenges in Large-Scale Agile

2021 ◽  
pp. 140-156
Author(s):  
Marthe Berntzen ◽  
Viktoria Stray ◽  
Nils Brede Moe
Keyword(s):  
Software Development ◽  
Large Scale ◽  
Development Program ◽  
Coordination Mechanisms ◽  
Agile Development ◽  
Team Coordination ◽  
Coordination Strategies ◽  
Development Teams ◽  
Development Methods

AbstractInter-team coordination in large-scale software development can be challenging when relying on agile development methods that emphasize iterative and frequent delivery in autonomous teams. Previous research has introduced the concept of coordination strategies, which refer to a set of coordination mechanisms to manage dependencies. We report on a case study in a large-scale agile development program with 16 development teams. Through interviews, meeting observations, and supplemental document analyses, we explore the challenges to inter-team coordination and how dependencies are managed. We found four coordination strategies: 1) aligning autonomous teams, 2) maintaining overview in the large-scale setting, 3) managing prioritizations, and 4) managing architecture and technical dependencies. This study extends previous research on coordination strategies within teams to the inter-team level. We propose that large-scale organizations can use coordination strategies to understand how they coordinate across teams and manage their unique coordination situation.

Texting as an Advising Communication Tool: A Case Study of Receptivity and Resistance

2021 ◽  
pp. 152102512110335
Author(s):  
Megan Tippetts ◽  
Bobbi Davis ◽  
Cathleen D. Zick
Keyword(s):  
Focus Group ◽  
Best Practices ◽  
Survey Data ◽  
Academic Advising ◽  
Academic Advisors ◽  
Communication Tool ◽  
Time Commitment ◽  
Over Time

Texting has been identified as a tool that has the potential to enhance informational exchanges between academic advisors and students. We use focus group and survey data from a recent texting intervention to assess student and advisor receptivity to texting as a new mode of communication. The data reveal that most students immediately saw the benefits of this new tool. In contrast, advisors initially were very skeptical of its value. They raised concerns about having a voice in the content of the messages and the time commitment that would be needed to respond to students’ texts. Over time, this feedback led to modifications in the texting protocol and, in turn, advisors came to view texting as an important mechanism for improving communication with students. Our study ends with a discussion of texting best practices within the context of academic advising.

Agile Assessment Methods and Approaches

2016 ◽  
pp. 165-174
Author(s):  
Mina Ziaei Nafchi ◽  
Taghi Javdani Gandomani
Keyword(s):  
Software Development ◽  
Measurement Methods ◽  
Assessment Methods ◽  
Agile Methods ◽  
Universal Model ◽  
Actual Position ◽  
Software Teams ◽  
Software Companies ◽  
Development Methods ◽  
Agile Teams

Agile methods are widely used in software companies in recent years. Many software companies are replacing their traditional development methods with agile methods. Nonetheless, measuring agility that they have achieved has been a topic of debate. Software teams and companies need to know how agile they are or how much is the agility degree of their organization. Unlike traditional methods in software development, there is no standard or universal model (like CMM/CMMI) to measure maturity of agile teams and software companies. So far, only a few methods and tools have been proposed to measure the agility of software companies. The main aim of this chapter is introducing the structure and main features of the existing agile assessment methods and providing a brief discussion on drawbacks of these methods. This chapter tries to elucidate the actual position of agility measurement methods in measuring agility degree of companies who are trying to adapt to agile methods and practices.

Sign in / Sign up

Export Citation Format

Share Document