Keywords

1 Introduction

Having high-performing agile software development teams is what most organizations operating in the field strive for. Among the numerous determinants of team performance, autonomy and trust deserve special attention when it comes to agile teams. Team autonomy is considered crucial for team performance because it allows teams to self-organize and make better decisions without needing to wait for approval [1, 2]. When it comes to team trust, it has been found to be one of the fundamentals of agile teams [3] as it creates favorable conditions for cooperation by strengthening the interactions between team members and improves problem-solving and overall software quality because team members that trust each other are more likely to share knowledge and report problems.

Although both team autonomy and trust are acknowledged as crucial for agile teams, there is a lack of theoretical explanation for how these factors impact performance. One possible explanation may be found in the Job Demands-resource model (JD-R), which depicts work engagement as a mediator of the relationships between job resources (e.g., team autonomy and trust) and performance [4]. In other words, factors such as team autonomy and trust may relate to work engagement, while work engagement, in its turn, relates to team performance.

Work engagement is in itself important for agile teams because it is closely related to the concept of motivation. According to the 5th principle in the agile manifesto, agile projects should be built around motivated individuals that have support and trust to get the job done. Motivation has been described as an important issue in software engineering [5], and job enthusiasm has been highlighted as the strongest predictor of developers’ productivity [6]. Motivated teams are also highly engaged, which means they are full of energy, enthusiastic about their work, and persist when facing drawbacks. Research shows that engaged teams outperform teams with low levels of engagement [7].

Recently the interest in work engagement is starting to emerge in the field of agile. For example, Huck-Fries et al. [8] demonstrate that work engagement in agile teams is indeed influenced by job resources and that agile practices are positively related to these resources. However, there is still insufficient insight into the effects of job resources and work engagement on the performance of agile software development teams. Against this background, we are suggesting the following research question: What are the effects of team autonomy and team trust on team work engagement and team performance in agile software development teams?

To answer this question, we develop and test a statistical research model that investigates how team autonomy and trust relate to team work engagement and how team work engagement mediates the relationship between these resources and team performance. We use survey data from 236 team members in 43 software development teams in Norway. Our results have important theoretical and practical implications for the field of agile development and contribute to the existing literature in several ways. First, we show how a well-established psychological theory (JD-R) can be successfully applied to examine agile teams. Second, we expand the research on JD-R theory by including the team level of analysis. And third, we provide valuable theoretical as well as practical insights by showing how team autonomy and trust relate to work engagement and performance of agile teams.

2 Related Work and Hypothesis Development

2.1 Team Work Engagement in Agile Software Development Teams

Software development teams now commonly adopt agile methods, which emphasize the importance of a collaborative, people-oriented approach with the use of self-organizing teams with high levels of autonomy [1, 9]. With the increased use of teams in software development, there is a growing recognition of factors that influence the performance of teams in this context. While the Agile Manifesto is based on the idea of highly motivated team members [10], empirical research on work engagement in the agile development literature is still limited.

Work engagement can be defined as a positive, fulfilling, work-related state of mind characterized by vigor, dedication, and absorption [11]. Vigor is described by high levels of energy while working and persistence in the face of difficulties. Dedication refers to being strongly involved in one’s work and experiencing a sense of significance, enthusiasm, and strong identification with the work. Absorption means being fully concentrated and immersed in one’s work and difficulties with detaching oneself from work. In sum, engaged employees feel full of energy, are enthusiastic about their work, and often lose track of time when working. Based on an abundant amount of research, work engagement has been found to have numerous benefits, such as organizational commitment, job satisfaction, extra-role behavior, and superior work performance, as well as increased well-being and general health [12]. Although most studies on work engagement focus on the individual level of measurement, the concept also exists at a team level [7, 13]. Team work engagement (TWE) describes a shared perception of work engagement of the team as a whole and can be defined as “a positive, fulfilling, and shared emergent motivational state that is characterized by team vigor, team dedication, and team absorption, which emerges from the interactions and shared experiences of members of a team” [13].

2.2 Work Engagement and the Job Demands-Resource Model

The JD-R model has frequently been used as a framework to explain the antecedents and consequences of work engagement [14]. According to the JD-R model, working conditions can be broadly classified into two categories; job demands and job resources. Job demands are the aspects of the job that require sustained physical and/or psychological effort and are therefore associated with certain costs. Examples are high work pressure, role conflict, and emotionally demanding interactions. Job resources refer to the job-related aspects that are functional in achieving work goals that allow employees to cope with the demanding aspects of their job and stimulate their learning and development [14]. Job resources may exist at different levels: the task level (e.g., job autonomy), the social level (e.g., team climate), and the larger organizational level (e.g., organizational justice). The JD-R model further suggests that job demands and job resources trigger two distinct psychological processes: health impairment and the motivational process. The health-impairment process posits that poorly designed jobs or constant job demands exhaust employees’ resources resulting in stress and health problems [15]. The motivational process, on the other hand, proposes that job resources both have intrinsic and extrinsic motivational potential and lead to high work engagement. Resources are intrinsically motivating because of their capacity to fulfill basic human needs such as autonomy, belongingness, and competence [16], and may also be extrinsically motivating because they translate into instrumental help that allows employees to successfully achieve work goals [14]. Research has consistently shown that job resources are the strongest predictors of work engagement due to their potential to enable employees to cope with demanding aspects of their job and, at the same time, stimulate personal growth, learning, and development [12, 17].

Some recent research indicates that agile work practices have a positive effect on work engagement through job resources [8, 18, 19]. Huck-Fries et al. [8] found, for instance, that agile practices significantly influenced the job resources of job autonomy and perceived meaningfulness, which again positively predicted team members’ work engagement. Similarly, Rietze and Zacher [19] demonstrated that agile work practices were positively related to job resources such as autonomy, peer support, and feedback and indirectly influenced work engagement via these job resources. Neither of these studies, however, studied job resources and work engagement at the team level. Further, the mediating effect of work engagement on the relationship between job resources and team performance is lacking in the previous studies on work engagement in agile software development teams. In the software engineering literature, team autonomy and team trust have continuously been identified as central to the effectiveness of agile software teams [3] and have also been recognized as important resources in the work engagement literature [20].

2.3 Team Work Engagement, Team Autonomy, and Trust

While many types of job resources may boost work engagement [14], previous meta-analyses and reviews suggest that resources at the task level, such as autonomy, are strong drivers for work engagement [17, 21]. Indeed, recent findings indicate that team autonomy is positively related to work engagement, suggesting that team members with a voice in allocating tasks, managing time, and defining leadership roles express greater vigor, dedication, and absorption at work [22]. Team autonomy is a key principle of agile practices and is recognized as an important condition for the responsiveness and effectiveness of agile software development teams [1]. Team autonomy can be defined as the extent to which the team has considerable discretion and freedom in deciding how to carry out tasks [23]. The increased levels of autonomy in the team bring decision-making authority directly to the operational level resulting in increased speed and accuracy of problem-solving [1]. The self-determination theory (SDT) also suggests that autonomy triggers the motivation of team members and may thus increase the level of engagement. Muecke and Greenwald [24] suggest that autonomy influences work engagement through both motivational and cognitive mechanisms, leading to job enrichment. The motivational perspective suggests that autonomy affects work engagement by influencing employees’ feelings of personal responsibility for work outcomes, feelings of mastery, and increased chances for learning and growth, all leading to higher motivation [25, 26]. The cognitive perspective focuses on the cognitive demands caused by job autonomy, such as increased problem-solving and information processing. As autonomy increases, employees are allowed to choose suitable strategies to deal with situations, resulting in more cognitive activities and higher cognitive demands that promote work engagement. Based on this review, we, therefore, hypothesize that: H1: Team autonomy is positively related to team work engagement.

Trust in the team represents a potentially vital job resource for agile teams because trust constitutes a central determinant of effective teamwork [27, 28] and has been found to play a crucial role in the functioning of teams in this context [3]. Trusting one’s teammates implies positive expectations about their actions and motivation grounded in the belief of their competence, integrity, and benevolence [29]. It is proposed that a high level of trust within the team can positively boost the team’s work engagement in several ways. For example, if team members trust their fellow teammates, they are confident that they have the competence to do their job and would not intentionally do anything to compromise them or the team. This could influence the motivation of team members and the collective engagement in the team. The confidence in their fellow team members may also increase their willingness to commit themselves to the goals [27] and increase their level of work engagement. By contrast, if team members lack confidence in their fellow team members and feel that they are not competent to do their tasks, they may not exert the effort and energy necessary for the team to succeed. In addition, if team members believe that their co-workers are consistent and would do what they say they will do, this could contribute to higher work engagement because they would be able to focus on achieving their tasks and goals as opposed to expending their energy and focus on monitoring and controlling actions of their fellow team members. Also, the support, mutual respect, and encouragement of fellow teammates provide team members with feelings of being accepted and cared for, satisfying their need for belonging and relatedness [16], thus increasing their work engagement. In addition, trust within the team has been found to facilitate the open sharing of knowledge and ideas in teams [28]. The increased sharing of knowledge and the presence of shared information may boost the team’s engagement [30]. Trust as a resource at the team level has not been extensively studied in the work engagement literature. However, related factors such as social support have frequently been included in the work engagement and JD-R studies. At the team level, Torrente et al. [7] found that social resources such as supportive team climate, collaboration, and teamwork were positively related to team work engagement. Based on this review, we hypothesize that: H2: Team trust is positively related to team work engagement.

2.4 Team Work Engagement as a Mediator Between Job Resources and Team Performance?

Both the JD-R model and the SDT propose that engagement leads to a higher level of performance because of the fulfillment of psychological needs, which enhances intrinsic motivation. Indeed, work engagement at the individual level has been found to predict task performance and extra-role performance [17]. Christian et al. [17] suggest that engaged employees are more persistent and pursue their tasks with more intensity, making them more focused on their work tasks and thus promoting higher task performance. While the empirical studies on team work engagement so far are relatively limited, some findings show a positive relationship between team work engagement team performance, with engaged teams outperforming teams with lower levels of engagement [7]. Explanations for this might be that engaged teams are able to maintain high motivational levels, resulting in greater commitment to collective goals and focused action on goal achievement [31]. Furthermore, engaged team members consider their work meaningful and relevant [32]. Also, engaged teams create a positive and activated affective climate that is characterized by high levels of energy and feelings of pleasure while working. This positive affective climate is beneficial for the performance of teams. Based on this, we hypothesize that: H3: Team work engagement is positively related to team performance.

The JD-R model proposes that work engagement mediates the impact of job resources on organizational outcomes [33]. Previous research has lent support for the mediating role of engagement, indicating that resources at the team level will have an indirect effect on team performance. Indeed, Torrente et al. [7] reported evidence for at mediation role of team work engagement between social resources and team performance in their sample of 63 teams. And Costa et al. [32] also showed that team members job resources positively affected work engagement and, consequently, team performance. In line with this, we propose H4: Team work engagement mediates the relationships between team autonomy and team performance. H5: Team work engagement mediates the relationships between team trust and team performance.

Taken together, we hypothesize that the job resources, team autonomy, and team trust will both be positively related to team work engagement (H1 and H2). Team work engagement again will positively influence team performance (H3) and will mediate the relationship between team autonomy and team performance (H4) and team trust and team performance (H5). Figure 1 illustrates our research model and hypotheses.

Fig. 1.
figure 1

The research model and the hypothesis

3 Method

In this section, we outline the sample and its context, the data collection process, the measures employed, and the statistical procedures used.

To test the proposed hypotheses, we conducted a quantitative study with survey data from software development teams in four companies in Norway, representing IT consultancy within software development and fintech. The teams included in the survey employ various agile practices, which are summarized in Table 1, along with information about the industry, number of employees, and number of teams included in the study.

Table 1. Description of the sample and its context

Email addresses from team members working in software teams were provided to the researchers, and the questionnaire was distributed and collected electronically via an online survey platform. All participants were given information about the purpose, data protection, and confidentiality before accepting the invitation to participate. In total, 239 team members from 45 teams responded. Two teams were excluded from the sample because they had fewer than three participants, leaving us with a final sample consisting of 236 team members from 43 teams, providing an overall response rate of 78 percent. The distribution of teams across the four organizations was 14, 10, 7, and 12. The team size ranged from 3 to 10 members, with an average of 5.5 members per team. A total of 72.7% of the participants were male, and the age distribution was as follows: 2.8% aged 18–24, 38.9% were 25–34, 34.1% were 35–44, 19% were 45–54, and 5.2% were 55 or older. All variables were measured with pre-existing validated measures. They were assessed on a Likert scale, ranging from 1 to 5 or 1 to 7.

Team autonomy was measured with six out of the eight original items from Langfred’s [23] team autonomy scale. This is a modified version of a well-validated scale for individual job autonomy, adapted to the team level. An example of an item from the scale is “The team is free to decide how to go about getting work done.” Team members were asked to assess how much they agreed with the statements concerning the team on a scale ranging from 1 (“completely disagree”) to 5 (“completely agree”).

Team trust was measured using a shortened version of the perceived trustworthiness in teams scale developed by Costa and Anderson [34]. An example item is: “In this team, people can rely on one another.” Responses ranged from 1 (completely disagree) to 5 (completely agree).

Team work engagement was measured using the 3-item scale from the ultra-short version of the Utrecht work engagement scale [35], adapted to the team level by following Costa et al. [13] using a reference shift from “I/me” to “we/our” to achieve the team focus. The items are: “In our team, we feel bursting with energy at our work,” “In our team, we are enthusiastic about our job,” and “In our team, we are immersed in our work.” The response alternatives ranged from 1 (“never the last year”) to 7 (“every day”).

Team performance was measured by three items based on scales developed by Jehn, Northcraft, and Neale [36]. Team members were asked to rate their team performance in terms of efficiency, quality, and overall performance. A sample item is: “How would you assess your team performance in terms of efficiency?” where the responses ranged from 1 (“very poor”) to 5 (“very good”).

Control variables included in the analysis were team size and time spent in the team, as these variables could potentially account for variance in the output variables. Team size was calculated based on how many team members from the team participated in the survey. We chose to proceed in this way because the average response rate per team was quite high (78%). The item for time spent in the team was “How much of your time do you work on this team?” (1 = less than 25%; 5 = around 90% or full-time). This measure was aggregated based on the scores provided by individual team members so that the scores represented the average for each team.

Data Aggregation.

As all hypotheses in the present study refer to the team level of analysis, we aggregated the initially individual-level data to the team level. All the variables, except team performance, assumed a referent-shift consensus model [37]. In a referent-shift model, the referent is directed towards the team because these constructs are collective in nature. Rather than asking team members about their own individual perceptions, referent shift incorporates the team as a whole. In contrast, role clarity and team performance assumed a consensus model [37] with the referent items directed at the individual team members because the construct resides in the individual’s own perception of how well the team performed. Both forms of models assume that team members share a common perception, and therefore, the interrater agreement is necessary to justify aggregation. To do this, we assessed the within-group agreement index rwg(j) [38] for all measures.

Data Analyses.

Data analyses were performed using Stata/MP version 16.1, which is a commonly applied software tool for statistical analyses. To test the hypothesis in the research model, we used partial least squares structural equation modeling (PLS-SEM) as the data analysis procedure. This procedure is recommended for data with relatively small sample sizes, and it allows for avoiding issues with non-normally distributed data [39]. The reliability and validity of the model were assessed by evaluating the measurement model (how well the latent variables reflect the variance in the measured items) [39]. This was done based on indicator reliability (item loadings’ size), composite reliability, convergent validity (average variance extracted (AVE), and discriminant validity [39]. Composite reliability was examined by evaluating Dillon-Goldstein’s rho (DG rho), which is an alternative to Cronbach’s alpha, in which the recommended level should be above 0.7. Discriminant validity (whether latent variables are sufficiently independent of each other) was assessed by comparing AVE values to the squared correlations among the latent variables in the model.

We tested the hypothesis by assessing the structural part of the model. To evaluate mediating relationships, one must compare the indirect paths suggested by the mediators to the direct paths [40]. Variables may have no mediating effect (the indirect effect is insignificant), a partial mediating effect (if the direct effect is significant), or a full mediating effect (if the direct effect is insignificant) [39]. The significance of the indirect effects was assessed based on bootstrap tests with 10 000 repetitions which is the procedure recommended by Hair et al. [39]. Finally, we tested potential common method bias (CMB) in the model through variance inflation factor (VIF), which is argued to be a reliable indicator of CMB in PLS-SEM [41]. Researchers argue that CMB can lead to results that are not due to the constructs of interest but rather to the measurement method, especially when it comes to behavioral research [42]. As a remedy, the assessment of VIF allows for uncovering possible multicollinearity in a PLS-SEM model [41].

4 Results

Since our study focuses on the team level, we first report the results of the within-group interrater agreement test that is recommended to justify the aggregation. As shown in Table 2, all average rwg(j) values are at about the threshold of 0.7, which, according to Le Breton and Senter [38], indicates acceptable interrater agreement within teams. This justifies us in aggregating the data collected at an individual level to a team level. Table 2 also shows average values and standard deviations of the aggregated variables.

Table 2. Summary of the aggregated variables for all teams

As shown in Table 3, all the standardized loadings are close to or above the recommended threshold of 0.7, AVE exceeds the recommended level of 0.5, and all D.G. Rho values are above the level of 0.7. These findings indicate acceptable indicator reliability, composite reliability, and convergent validity.

Table 3. The measurement model (step 3)

All AVE values (Table 3) are larger than the squared correlations among the latent variables in the model, which suggests acceptable discriminant validity of the measurement model.

Table 4. Discriminant validity (Squared correlations < AVE)

Table 4 summarizes both direct and indirect effects in the model with “team work engagement” (TWE) and “team performance” as outcomes. Taking into account the potential relationship between “team autonomy” and “team trust” as job resources, we present the coefficients in a stepwise fashion. In Step 1, we entered “team autonomy” as a predictor, whereas “team trust” was entered in Step 2 and the control variables in Step 3. All the significant effects are highlighted in bold (Table 4).

In Step 1 we see that “team autonomy” has a positive direct effect on “team work engagement” (β = .453, p < .01), whereas “TWE” in turn has a positive effect on “team performance” (β = .613, p < .001). This means that teams with higher autonomy could be expected to also have a higher level of work engagement; and that the teams where the members were highly engaged also showed increased performance. There was no significant direct effect of “team autonomy on “team performance”, whereas the indirect effect was significant (β = .277, p < .05). The combined findings at this step show an indirect-only mediation (according to Zhao et al. [40]) between “team autonomy” and “team performance” (β = .277, p < .05), meaning that “TWE” fully mediated the relationship between the two variables. For this step, we could conclude that “team autonomy” functions as a job resource, thus strengthening teams’ engagement which then leads to subsequent increased performance.

Table 5. Summary (stepwise) of the effects with standardized path coefficients

In Step 2, we entered “team trust” as the second independent variable in the model. As shown in Table 5, “team autonomy” had neither direct nor indirect effect on “team performance” when controlled for “team trust”. At the same time, “team trust” showed a strong direct effect on “team work engagement” (β = .487, p < .01), which indicates that teams with a high level of trust were often highly engaged in their work. We also observed a significant indirect effect of “team trust” on “team performance” mediated by “TWE” (β = .241, p < .01). Since “team trust” did not have any direct effect on “team performance”, we concluded an indirect-only mediation (full mediation) between these two variables. We concluded that in Step 2 “TWE” fully mediated the relationship between “team trust” and “team performance” when controlled for “team autonomy”. In other words, “TWE” functioned as a mediator between “team trust” and “team performance”, but not between “team autonomy” and “team performance”, as it was in Step 1 when we did not control for “team trust”. In Step 3, the same results were validated by entering the control variables. Again, we saw that “team trust” had a significant indirect effect on “team performance” mediated by “TWE” (β = .223, p < .01), but no such effect was observed for “team autonomy”. As no control variable had either a significant direct or indirect effect on the dependent variables and the effects from Step 2 stayed significant (Table 4), we concluded that the findings could not be attributed to the properties of the particular teams. The overall conclusion from the analysis is that both “team autonomy” and “team trust” may function as team work resources, affecting “team work engagement” and eventually “team performance”. However, “team autonomy” as a work resource seems to have a weaker effect than “team trust”. Finally, all VIF values in the model ranged between 1.017 and 1.754, which is lower than the threshold of 3 recommended by Hair et al. [39] for PLS-SEM. This, in combination with other reliability diagnostics, indicates that the findings are not solely due to the measurement method.

5 Discussion

Team autonomy and team trust have long been acknowledged as fundamentals of agile teams [1, 3]. Our study indicates that these factors do not directly affect the performance of such teams but instead may affect team work engagement. Further, team work engagement seems to have a strong effect on team performance, thus indirectly linking it back to trust and - to a smaller extent – to team autonomy. In this way, our results confirm that work engagement is significant for the performance of agile teams [5, 6]. The results are summarized in Table 6.

Table 6. Summary of the results and implications

The absence of the direct effect of autonomy on performance and its weakened effect on team work engagement may sound surprising as autonomy consistently has been described as one of the fundamental needs of agile teams [1] and also one of the key characteristics in many work-stress models and theories (e.g., [26]). However, the strength of the relationship between autonomy and work engagement has been found to vary across studies [20]. This can partially be explained by the so-called autonomy paradox, meaning that greater autonomy can have both positive (e.g., increased control over tasks) and negative effects (increased stress due to increased job demands and expectations of their contribution to organizational performance) [22]. We follow Hakanen et al. [20], suggesting that the engaging power of autonomy is not so straightforward in the context of agile teams with complex tasks and organizational contexts.

Our findings indicate that team trust plays an important role in fostering work engagement and further enhancing team performance in agile teams. This is in line with the proposition of Moe et al. that mutual trust is of fundamental importance for agile teams and that teams that had not established mutual trust use more time on discovering and acknowledging issues [3]. Another explanation for our findings is the possible interaction between autonomy and trust. Our results indicate that the level of trust may impact the effect of team autonomy on engagement and performance. This corresponds to the findings in our recent study [43], showing that team autonomy positively affects psychological safety, a distinct but related construct of trust. Other studies also highlight lack of trust as one of the potential barriers to team autonomy [44]. We, therefore, invite researchers to further investigate whether and how team trust and team autonomy interact to affect the level of engagement in agile teams.

6 Limitations and Future Work

While providing valuable contributions to the literature, this study also has some limitations. First, the research model in our study is confined to a limited number of team-level factors influencing team work engagement and team performance. The reality for teams in organizations is obviously much more complex, with a daunting number of other factors, both on the individual, team, and organizational level, that impact the work and performance. The present study examines how job resources (trust, autonomy) and work engagement relate to the performance of agile software development teams and is a first step in understanding the factors impacting teams’ engagement and performance in this setting. We acknowledge that there are several organizational and technical factors that could impact the engagement and performance of software development teams. Forsgren, Humble, and Kim [45], for instance, identified 24 capabilities that drive software delivery performance, including organizational culture, leadership, and architectural aspects. We thus encourage researchers to test more complex research models to further explore the effect of job resources at different levels that are relevant for the engagement and performance of agile software development teams. Second, the cross-sectional nature of our data does not allow us to conclude causality between the variables (for example, that work engagement leads to better team performance or vice versa). We are thus left with only indications of causality derived from theory and previous research. Future research should be conducted using a time-lagged design in order to examine the causal relationships between team autonomy and team work engagement; and team work engagement and performance. Further, self-reported data was the only foundation of the study. For example, we did not apply external actors’ evaluation of the teams’ performance, which may have biased the performance scores. Still, we believe that a strong relationship between teams’ trust and work engagement; and between work engagement and their own perception of performance is a valuable result that deserves further investigation. We invite researchers to validate whether this result holds when additional measures of performance are also applied. Finally, the self-reported data may have inflated the correlations among the variables and thus potentially suffer from Common Method Bias (CMB). However, pre-existing measures were used, and statistical procedures for PLS-SEM were undertaken to reduce the risk of CMB.

7 Implications and Conclusion

Our results provide valuable theoretical insights and also have important practical implications for agile teams. The study demonstrates the theoretical value that the JD-R model and the work engagement literature can provide for agile research. Work engagement is a meaningful construct at the team level that mediates the impact of job resources on performance in teams. The overall results indicate that highly engaged teams are also likely to perform their tasks more efficiently and effectively, thus generating a competitive advantage. Agile practitioners should therefore promote team-based resources that contribute to engagement in their teams. Our findings suggest that both increasing the level of autonomy and, more importantly, building trust in the teams can foster team engagement, which in its turn has the potential to enhance the performance of agile teams. The “social fabric” of the teams plays an important role for team engagement and performance probably because succeeding in agile software development teams requires honest feedback, communication and collective problem-solving. We, therefore, urge practitioners to provide opportunities for teams to build trusting relationships where team members can demonstrate their competence, integrity, and benevolence.