Stress is an important workplace issue, affecting both the health of individuals, and the health of organizations. Early advocacy for Agile Software Development suggested it might help avoid stress, with practices that emphasize a sustainable pace, and self-organizing teams. Our analysis of a 2014 survey, however, suggested that stress might still be commonplace in Agile teams, especially for those with less experience. We also noticed that newcomers to Agile emphasized technical, rather than collaborative, practices, and speculated this might explain the stress. We explored this in our analysis of a follow-up survey conducted in 2016, and report our findings in this paper. We show that there are a variety of factors involved, and that avoiding stress is associated with both collaborative and technical practices, and a range of outcomes.

Additional Metadata
Keywords Agile, Software development, Stress
Persistent URL dx.doi.org/10.1007/978-3-319-91602-6_18
Series Lecture Notes in Business Information Processing
Citation
Meier, A. (Andreas), Kropp, M. (Martin), Anslow, C. (Craig), & Biddle, R. (2018). Stress in agile software development: Practices and outcomes. In Lecture Notes in Business Information Processing. doi:10.1007/978-3-319-91602-6_18