Requirement Changes and Project Success: The Moderating Effects of Agile Approaches in System Engineering Projects

Maierhofer, Sabine; Stelzmann, Ernst Stefan; Kohlbacher, Markus; Fellner, Björn

doi:10.1007/978-3-642-15666-3_6

Cited by 6 publications

(5 citation statements)

References 14 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…This is expected in agile environments. However, Maierhofer et al's findings show that continuous customer integration does not mitigate negative effects of RC on project success in agile [21]. Additionally, business analyst not being the carrier in environments where the role is present, suggests that business analyst is not being able to play his/her role with customer collaboration, which might give a drop in his/her contentment of doing the job.…”

Section: Discussionmentioning

confidence: 95%

A Multi-dimensional Study of Requirements Changes in Agile Software Development Projects

Madampe,

Hoda,

Grundy

2020

Preprint

View full text Add to dashboard Cite

Agile processes are now widely practiced by software engineering (SE) teams, and the agile manifesto claims that agile methods support responding to changes well. However, no study appears to have researched whether this is accurate in reality. Requirements changes (RCs) are inevitable in any software development environment, and we wanted to acquire a holistic picture of how RCs occur and are handled in agile SE teams in practice. We also wanted to know whether responding to changes is the only or a main reason for software teams to use agile in their projects. To do this we conducted a mixed-methods research study which comprised of interviews of 10 agile practitioners from New Zealand and Australia, a literature review, and an in-depth survey with the participation of 40 agile practitioners world-wide. Through this study we identified different types of RCs, their origination including reasons for origination, forms, sources, carriers, and events at which they originate, challenging nature, and finally whether agile helps to respond to changes or not. We also found that agile teams seem to be reluctant to accept RCs, and therefore, they use several mitigation strategies. Additionally, as they accept the RCs, they use a variety of techniques to handle them. Furthermore, we found that agile allowing better response to RCs is only a minor reason for practicing agile. Several more important reasons included being able to deliver the product in a shorter period and increasing team productivity. Practitioners stated this improves the agile team environment and thus are the real motivators for teams to practice agile. Finally, we provide a set of practical recommendations that can be used to better handle RCs effectively in agile software development environments.

show abstract

Section: Discussionmentioning

confidence: 95%

A Multi-dimensional Study of Requirements Changes in Agile Software Development Projects

Madampe,

Hoda,

Grundy

2020

Preprint

View full text Add to dashboard Cite

show abstract

“…But Research on the interdependencies between requirement changes, the agile practices and customer satisfaction in such System Engineering projects has been limited to date [20]. Therefore this paper focused on Systems Engineering projects which develop products consisting of hard-and software.…”

Section: Discussionmentioning

confidence: 99%

Do agile software development practices increase customer satisfaction in Systems Engineering projects?

Kohlbacher

Stelzmann

Maierhofer

2011

2011 IEEE International Systems Conference

Self Cite

View full text Add to dashboard Cite

This paper investigates the effects of applying agile software development practices within Systems Engineering projects. In particular it should be found out whether agile methods are able to mitigate negative effects of requirement changes on project performance. Customer satisfaction is chosen as performance factor. 72 system developing companies are surveyed that develop products consisting of hard-and software. Since agile methods have been successfully applied within software development our hypothesis is that they could also be successfully applied within Systems Engineering. Our study focuses on 6 specific agile practices and their ability to improve customer satisfaction in complex hard-and software projects. It is shown that some of them have a positive effect on customer satisfaction but we do not find evidence for others.

show abstract

“…This paper aims to evaluate the relation between change in requirements and agile methods on project succeed. This paper also uses regression models to measure project succeed in order to requirement changes and efficient execution [17]. This paper cannot find evidence that two dimensions of agile software projects are highly correlated.…”

Section: Related Workmentioning

confidence: 99%

Multiple Linear Regression for Determining Critical Failure Factors of Agile Software Projects

Abdelaziz¹,

Darwish²,

Hefny³

2019

IJIES

View full text Add to dashboard Cite

The management of agile software projects plays an important role in the success or failure of projects. There are many factors of success or failure that clearly affect agile software projects. There is a big problem in not having a formal study to identify critical failure factors that assess the success or failure of projects accurately. This paper focuses on failure factors of agile software projects. This paper seeks to configure a formal study by using multiple regression analysis for identifying critical failure factors to avoid projects failure, thus saving time and money for the stakeholders. The proposed model is implemented by using R programming. The proposed model also is implemented by two models. The first model based on critical failure factors (CFF) of agile software projects. The second model based the failure factors of the proposed in the initial list (FFIL). The model of CFF outperforms on the model of FFIL in order to accuracy by 10.7% and random error ratio by 4.8%. The results revealed that only 10 out of 19 hypotheses were supported, identifying seven critical failure factors for Agile software development projects: (a) Organizational culture too traditional, (b) Lack of agile logistical arrangements,(c) Lack of project management competence, (d) Lack of team work, (e) Bad customer relationship, (f) defined project scope, and (g) defined project planning.

show abstract

Requirement Changes and Project Success: The Moderating Effects of Agile Approaches in System Engineering Projects

Cited by 6 publications

References 14 publications

A Multi-dimensional Study of Requirements Changes in Agile Software Development Projects

A Multi-dimensional Study of Requirements Changes in Agile Software Development Projects

Do agile software development practices increase customer satisfaction in Systems Engineering projects?

Multiple Linear Regression for Determining Critical Failure Factors of Agile Software Projects

Contact Info

Product

Resources

About