How Agile Is Hybrid Agile? An Analysis of the HELENA Data

Noll, John; Beecham, Sarah

doi:10.1007/978-3-030-35333-9_25

Cited by 15 publications

(13 citation statements)

References 20 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…That is, there is no case that, for instance, is usually traditional and shifts to agile when using a specific method or practice. This is in line with Noll and Beecham [42], who found method combinations tend to "stay in their class", e.g., findings are confirmatory, that projects that mainly use agile methods are more likely to use agile practices. Yet, no single practice determines whether a project is agile or not.…”

Section: 321supporting

confidence: 88%

“…But software engineering is not a philosophy, it is a concrete part of our day-to-day lives, we depend on it. The HELENA data research has started to create theories [42], yet, future research must put more emphasis on theorizing software engineering.…”

Section: General Challenges In Software Engineeringmentioning

confidence: 99%

“…Agile Teams in Globally Distributed Settings: Recent research [42] suggests that hybrid organizations have in average a lower degree of agility. Most distributed software projects are neither purely agile or purely traditional in their approach to software development, but rather combine agile and traditional methods.…”

Section: General Challenges In Software Engineeringmentioning

confidence: 99%

See 2 more Smart Citations

What Makes Agile Software Development Agile?

Kuhrmann

Tell

Hebig

et al. 2022

IIEEE Trans. Software Eng.

Self Cite

View full text Add to dashboard Cite

Together with many success stories, promises such as the increase in production speed and the improvement in stakeholders' collaboration have contributed to making agile a transformation in the software industry in which many companies want to take part. However, driven either by a natural and expected evolution or by contextual factors that challenge the adoption of agile methods as prescribed by their creator(s), software processes in practice mutate into hybrids over time. Are these still agile? In this article, we investigate the question: what makes a software development method agile? We present an empirical study grounded in a large-scale international survey that aims to identify software development methods and practices that improve or tame agility. Based on 556 data points, we analyze the perceived degree of agility in the implementation of standard project disciplines and its relation to used development methods and practices. Our findings suggest that only a small number of participants operate their projects in a purely traditional or agile manner (under 15%). That said, most project disciplines and most practices show a clear trend towards increasing degrees of agility. Compared to the methods used to develop software, the selection of practices has a stronger effect on the degree of agility of a given discipline. Finally, there are no methods or practices that explicitly guarantee or prevent agility. We conclude that agility cannot be defined solely at the process level. Additional factors need to be taken into account when trying to implement or improve agility in a software company. Finally, we discuss the field of software process-related research in the light of our findings and present a roadmap for future research.

show abstract

Section: 321supporting

confidence: 88%

Section: General Challenges In Software Engineeringmentioning

confidence: 99%

Section: General Challenges In Software Engineeringmentioning

confidence: 99%

See 1 more Smart Citation

What Makes Agile Software Development Agile?

Kuhrmann

Tell

Hebig

et al. 2022

IIEEE Trans. Software Eng.

Self Cite

View full text Add to dashboard Cite

show abstract

“…In our systematic mapping study, we investigate publications that are concerned with the combination of agile and plan‐based approaches. The combination of agile and plan‐based approaches is called hybrid development approaches in literature 8,26 . Because we concentrate our work on software development and to keep the phrase as generic as possible, we chose hybrid software development as one key‐phrase.…”

Section: Methodsmentioning

confidence: 99%

“…The study was published in 2017 and resulted in 1467 data points with 691 complete answers 25 . Noll and Beecham 26 analyzed the data and found out that in 66% of the cases an APH approach was used. They state that the use of more agile or plan‐based methods depends rather on the mindset than technical factors.…”

Section: Background and Related Workmentioning

confidence: 99%

Goals and challenges in hybrid software development approaches

Prenner

Unger‐Windeler

Schneider

2021

J Software Evolu Process

View full text Add to dashboard Cite

The number of companies that use agile methods increases steadily. However, these companies often do not implement a pure agile approach but combine agile and plan‐based methods to so‐called hybrid development approaches. However, the development of these approaches is rather difficult for the companies, since agile and plan‐based approaches often follow opposite concepts. To benefit from agile and plan‐based approaches at the same time, the companies have to identify and address the conflicts between agile and plan‐based methods. The conflicts depend on the goals that are pursued with the implementation of agile and plan‐based methods. However, there is no overview of the exact goals that are pursued in hybrid approaches and which challenges and conflicts arise with them. Therefore, we conducted a systematic mapping study to gather and analyze the goals and challenges in hybrid development approaches. The mapping study is focused on literature that presents the actual needs and goals of companies and projects. Based on our results, we present the influence factors that cause conflicts in hybrid approaches and discuss how these conflicts can be addressed.

show abstract

Project Management Issues While Using Agile Methodology

Butt

Piñeres-Espitia

Ariza-Colpas

et al. 2022

Lecture Notes in Business Information Processing

View full text Add to dashboard Cite

Software engineering has many software development life cycle (SDLC) models to develop a software application and the latest SDLC models have been provided by agile methods. The agile methodology has been introduced due to some existing lacks in software development. Now agile methodology is used to overcome these deficiencies and improve software development. The use of the agile methodology is increased within software industries due to its distinctive features such as enabling change requests from the client at any stage of a project, client satisfaction, iterative development, and clientdeveloper interaction. Another reason for agile adoption is the methods that are being used for agile software development. These methods include Scrum, Feature drive development, Extreme programming, and Dynamic system development methods. However, the agile methodology has some issues for project development and management. In this study, we discuss all these issues which are related to agile methods and individuals (i.e. team and developer). Further, we suggest the possible improvements that need to be introduced in the agile methodology. We believe such improvements is to make the agile methodology more productive for development environments.

show abstract

How Agile Is Hybrid Agile? An Analysis of the HELENA Data

Cited by 15 publications

References 20 publications

What Makes Agile Software Development Agile?

What Makes Agile Software Development Agile?

Goals and challenges in hybrid software development approaches

Project Management Issues While Using Agile Methodology

Contact Info

Product

Resources

About