Satisfaction and its correlates in agile software development

Abstract

In this paper we address the topic software development team members satisfaction with their development process. We present an in-depth analysis of the results of a nationwide survey about software development in Switzerland. We wanted to find out if satisfaction relates to the applied development method, and to the use of various practices, and influences on business, team and software issues. We found that higher satisfaction is reported more by those using Agile development than with plan-driven processes. We explored the di↵erent perspectives of developers and those with a management role and found a high consistency of satisfaction between Agile developers and Agile management, and di↵erences with those using working plan-driven methods. We found that certain practices and influences have high correlations to satisfaction, and that collaborative processes are closely related to satisfaction. We then explored the relationship between satisfaction and various other perspectives. Our results in this analysis are principally descriptive, but we think they can be a relevant contribution to understand the challenges for everyone involved in Agile development.

The affective, behavioural and cognitive outcomes of agile project management: A preliminarymeta‐analysis

“…This heterogeneity of affective reactions to APM between individuals may be larger than reactions to other organizational phenomena, such as leadership. While many employees may experience working in agile projects as positive, some may perceive it as negative (see Kropp et al, 2020 for an in‐depth analysis). While positive leadership styles seem to have universal positive effects (see, e.g., Decuypere & Schaufeli, 2021), APM could require a person‐organization fit perspective.…”

Agile adoption challenges in insurance: a systematic literature and expert review

“…Agile develop software that is grouped and broken into smaller, backlogged and more specialized deliverables. Moreover, the agile method is direct to the waterfall method for enlarging and testing software incrementally [10]. The contrasts between agile development and conventional development are based on an unpredictable reality, as well as stressing the value skilled people and their relationships contribute to software development.…”

“…Moreover, team and project work domains were escalated by eleven and eight research. [15], [19], [24], [28], [31], [32], [34] Planning 9 [6], [10], [20], [23]- [25], [31], [33], [34] Project work 11 [6], [10], [15], [19], [20], [23]- [25], [30], [32], [34] Delivery 10 [6], [10], [19], [21], [24], [25], [27], [29], [31], [33] Measurement 3 [24], [25], [33] Uncertainty 9 [6], [20], [21], [23], [24], [26], [27], [32], [33]…”

Do Agile scaling approaches make a difference? an empirical comparison of team effectiveness across popular scaling approaches

“…In the context of Agile teams, job satisfaction has been found to correlate positively with Agile practices and the ability to achieve business impact with one's work (Kropp et al 2020;Tripp et al 2016;Keeling et al 2015). Another perspective is provided by Verwijs and Russo (2023b).…”

“…Stakeholder satisfaction has been proposed as a key indicator of success for Agile teams (Kupiainen et al 2014;Mahnic and Vrana 2007). At the same time, job satisfaction and high team morale have been associated with team effectiveness (Verwijs and Russo 2023b;Kropp et al 2020;Tripp et al 2016). Henceforth, we frame our research question (RQ) as follows:…”