Experience-Based Approach for Adoption of Agile Practices in Software Development Projects

Krasteva, Iva; Ilieva, Sylvia; Dimov, Aleksandar

doi:10.1007/978-3-642-13094-6_22

Cited by 5 publications

(5 citation statements)

References 18 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Another important number of extensions are intended to model certain aspects of some specific kinds of processes, which cannot be completely supported with the current SPEM specification. For instance, processes based on agile practices [26], agent-oriented [27] methodologies, or user interface development methods [28].…”

Section: Extensions To the Meta-modelmentioning

confidence: 99%

Uses and applications of Software & Systems Process Engineering Meta‐Model process models. A systematic mapping study

Ruiz-Rube

Dodero

Palomo-Duarte

et al. 2013

J Software Evolu Process

View full text Add to dashboard Cite

SUMMARYSoftware process engineering is a discipline, which aims to study and improve software development and maintenance processes. The explicit definition of software processes is essential. To this end, the Object Management Group consortium proposed the Software & Systems Process Engineering Meta-Model (SPEM) that exploits the benefits of the Model Driven Architecture paradigm applied to software process models, instead of software specification models. The aim of this study is to discover evidence clusters and evidence deserts in the use and application of SPEM from a business process management point of view. To reach the proposed objective, we have undertaken a systematic mapping study of the existing scientific literature.The reviewed literature deals mainly with process modeling and, to a lesser extent, with process adaptability, verification, and validation, enactment and evaluation. Wide agreement exists in using the SPEM meta-model to develop different types of methods and processes. Further research efforts are needed in areas related to enactment and evaluation of software processes. There is a need to evolve to a new version of the meta-model that incorporates the improvements proposed by different authors.

show abstract

Section: Extensions To the Meta-modelmentioning

confidence: 99%

Uses and applications of Software & Systems Process Engineering Meta‐Model process models. A systematic mapping study

Ruiz-Rube

Dodero

Palomo-Duarte

et al. 2013

J Software Evolu Process

View full text Add to dashboard Cite

show abstract

“…Their approach supports the orderly adoption of agile practices to the software development method of an organization by reviewing research on the applicability of agile practices when particular situation factors are present. 58 It is based on an iterative and incremental process that is adaptable to project characteristics and customizable through the execution of the project. Moreover, the approach is based on four meta-models that enable the automated generation of the appropriate software development process.…”

Section: Systematic Approaches For Agile Methods Tailoringmentioning

confidence: 99%

“…The model of actions best suited to this context is “sense‐analyze‐respond”, that is, sense incoming data, analyze that data and then respond in accordance with expert advice and interpretation of that analysis 73,74 . As a matter of fact, all existing approaches for agile method tailoring 56–58 unconsciously exploit this model. However, building a method repository requires too much up‐front investment and does not guarantee the matching between the specific situation and context at hand and the information that is available in the repository.…”

Section: Methodsmentioning

confidence: 99%

“…Krasteva et al delivered an experience‐based approach to situational engineering of agile methods. Their approach supports the orderly adoption of agile practices to the software development method of an organization by reviewing research on the applicability of agile practices when particular situation factors are present 58 . It is based on an iterative and incremental process that is adaptable to project characteristics and customizable through the execution of the project.…”

Section: Background and Related Workmentioning

confidence: 99%

See 1 more Smart Citation

Scaling scrum with a customized nexus framework: A report from a joint industry‐academia research project

2023

View full text Add to dashboard Cite

Despite a wide range of scaling frameworks available, large‐scale agile transformations are not straightforward undertakings. Few organizations have structures in place that fit the predefined workflows – while once one applies an off‐the‐shelf framework outside of its prescribed process, guidance quickly runs out. In this paper, we demonstrate how to instantiate a method configuration process using a lightweight experimental approach embedded in Action Research cycles. The proposed approach was developed to assist practitioners working on a multiple‐team project at Intel Technology Poland to find the right practices to continue their Nexus‐based transformation and integrate their in‐house method into the already established company structures, processes, and routines. In particular, it enabled identifying a series of challenges with scaled practices and coping with those. The challenges ranged from logistical problems, through poor availability of the Product Owner, to lackluster knowledge transfer and a wide array of communication/coordination issues at meetings. The study broadens the current body of knowledge within technology management and the scaled agile method‐tailoring domain. It indicates potential corrective actions that may be taken advantage of by entities that are not inclined, due to organizational constraints, to directly implement an off‐the‐shelf framework. Furthermore, our study demonstrates that a gradual transition to large‐scale agile at the project level (1) is possible with the preservation of traditional command‐and‐control management practices; (2) requires neither middle management involvement nor upfront investment; and (3) does not need to disrupt the continuous delivery of the product.

show abstract

“…To overcome the issues mentioned in previous paragraph, some studies on frameworks supporting Agile SD implementation have Agile 39 52 9 Projects Waterfall 11 60 29 Large size Agile 18 59 23 Projects Waterfall 3 55 42 Medium size Agile 27 62 11 Projects Waterfall 7 68 25 Small size Agile 58 38 4 Projects Waterfall 44 45 11 Note: The resolution of software projects from FY2011-2015 within the new CHAOS database, segmented by the Agile process and waterfall method. The total number of software projects is over 10,000 Source: Chaos Report 2015been conducted, primarily in the knowledge management area (Sidky et al, 2007;Sureshchandra and Shrinivasavadhani, 2008;Mannaro, 2008;Qumer and Henderson-Sellers, 2008;Soundararajan and Arthur, 2009;McAvoy and Butler, 2009;Esfahani et al, 2010;Krasteva et al, 2010;Esfahani, 2012;Lee and Yong, 2013;Nikitina and Kajko-Mattsson, 2014;Rasnacis and Berzisa, 2016;Hoda and Noble, 2017;Pries-Heje and Baskerville, 2017). Furthermore, some researchers have focused on the factors that refer to the learning process, but only a few have included human factors as determinants (Qumer and Henderson-Sellers, 2008;McAvoy and Butler, 2009;Soundararajan and Arthur, 2009;Lee and Yong, 2013;Nikitina and Kajko-Mattsson, 2014;Hoda and Noble, 2017;Pries-Heje and Baskerville, 2...…”

mentioning

confidence: 99%

Uncovering the failure of Agile framework implementation using SSM-based action research

et al. 2020

View full text Add to dashboard Cite

It is undeniable that the Agile software development (SD) framework has been commonly used in information technology projects. However, many of the early adopters failed to implement it properly. Some researchers had proposed a solution by using the adaptation framework as a support, but they cannot clearly explain its development. Furthermore, the correlation between adaptation framework and problem solving is dubious. This study reviews and discusses the literature and empirical studies on the failure of Agile SD implementation by revisiting the supporting framework that used to comprehend the issues in Agile SD implementation. A comparative approach is used to review the literature available in academic databases, such as ProQuest, EBSCO, IEEE, and Scopus, to ensure research originality and novelty. By filtering 87 papers that met the initial criteria, only 4 researchers focused on the area of knowledge management and used the learning process as a supporting framework in Agile SD implementation. However, they did not clearly explain the development of the framework for Agile SD. The author's initial research on a corporation reveals the failure of Agile SD implementation. Soft systems methodology (SSM)-based action research (AR) proposed to identify the real issues in Agile SD implementation. SSMbased AR provides a solution by clarifying the development of a framework using tacit and explicit knowledge to validate the development process. This study can help practitioners and academics understand the process of Agile SD implementation by early adopters who still need assistance with its application. This study is the first to explore Agile SD implementation in a corporation using the experience-based approach, contributing to knowledge improvement. It contributes to the scholarly literature by presenting concepts that combine humancentric aspects and knowledge management to improve the learning in the organization.

show abstract

Experience-Based Approach for Adoption of Agile Practices in Software Development Projects

Cited by 5 publications

References 18 publications

Uses and applications of Software & Systems Process Engineering Meta‐Model process models. A systematic mapping study

Uses and applications of Software & Systems Process Engineering Meta‐Model process models. A systematic mapping study

Scaling scrum with a customized nexus framework: A report from a joint industry‐academia research project

Uncovering the failure of Agile framework implementation using SSM-based action research

Contact Info

Product

Resources

About