Búsqueda avanzada

Resultados de búsqueda para Agile software development

(Artículo relevante) Agile-CMMI Alignment: Contributions and To-Dos for Organizations

CMMI and Agile can work together. Over 80% of CMMI appraisals in 2018 were conducted at agile organizations, even though pre-2018 CMMI versions do not provide guidelines for agile contexts. A number of experience reports and research studies address the alignment between the two approaches but also pinpoint open tactical and organizational challenges. CMMI V2.0, published in 2018, was designed to be understandable, accessible, and flexible. It was intended to be integrated with other methodologies such as Agile. In this paper, we discuss to what extent the new CMMI V2.0 addresses the existing Agile-CMMI alignment challenges. We identify the two most significant CMMI V2.0 artifacts for this aim, the context-specific sections provided for most of the practice areas, and the value statements linked to the practices. We analyze how they contribute to each of the existing challenges and highlight important issues that organizations still need to tackle regarding this alignment.

Autores: Valeria Henriquez / Ana M. Moreno / Jose A. Calvo-Manzano / Tomas San Feliu / 
Palabras Clave: Agile and CMMI-DEV V2.0 - Agile software development - CMMI V2.0 - Software process Improvemen

Management of quality requirements in agile and rapid software development: A systematic mapping study

Context. Quality requirements (QRs) describe the desired quality of software, and they play an important role in the success of software projects. In agile software development (ASD), QRs are often ill-defined and not well addressed due to the focus on quickly delivering functionality. Rapid software development (RSD) approaches (e.g., continuous delivery and continuous deployment), which shorten delivery times, are more prone to neglect QRs. Despite the significance of QRs in both ASD and RSD, there is limited synthesized knowledge on their management in those approaches.Objective.This study aims to synthesize state-of-the-art knowledge about QR management in ASD and RSD, focusing on three aspects: bibliometric, strategies, and challenges.Research method.Using a systematic mapping study with a snowballing search strategy, we identified and structured the literature on QR management in ASD and RSD.Results.We found 156 primary studies: 106 are empirical studies, 16 are experience reports, and 34 are theoretical studies. Security and performance were the most commonly reported QR types. We identified various QR management strategies: 74 practices, 43 methods, 13 models, 12 frameworks, 11 advices, 10 tools, and 7 guidelines. Additionally, we identified 18 categories and 4 non-recurring challenges of managing QRs. The limited ability of ASD to handle QRs, time constraints due to short iteration cycles, limitations regarding the testing of QRs and neglect of QRs were the top categories of challenges.Conclusion.Management of QRs is significant in ASD and is becoming important in RSD. This study identified research gaps, such as the need for more tools and guidelines, lightweight QR management strategies that fit short iteration cycles, investigations of the link between QRs challenges and technical debt, and extension of empirical validation of existing strategies to a wider context. It also synthesizes QR management strategies and challenges, which may be useful for practitioners.

Autores: Woubshet Behutiye / Pertti Karhapäa / Lidia Lopez / Xavier Burgués / Silverio Martínez-Fernández / Anna Maria Vollmer / Pilar Rodríguez / Xavier Franch / Markku Oivo / 
Palabras Clave: Agile software development - Non-functional requirements - quality requirements - Rapid software development - Systematic literature reviews - Systematic Mapping Study

Change-Impact driven Agile Architecting

his summary presents a solution based on the use of change-impact knowledge as the main driver for agile architecting. The solution consists of a Change Impact Analysis technique and a set of models to assist agile architects in the change (decision-making) process by retrieving the change-impact architectural knowledge resulting from adding or changing features iteration after iteration.

Autores: Jessica Díaz / Jennifer Pérez / Juan Garbajosa / Agustín Yagüe / 
Palabras Clave: agile architecting - Agile software development - change-impact analysis

No encuentra los resultados que busca? Prueba nuestra Búsqueda avanzada