Team-Enacted Use vs. Developer-Needed Use of Agile Practices: How Perceptual (In-)Congruence and Team Feedback-Seeking Shape Developer Well-Being

Are agile practices always beneficial for developers? Although agile methods, such as daily stand-ups or pair programming, are designed to enhance flexibility and productivity, developers often experience a mismatch between the team-enacted use of these practices and their own individual needs. Using daily survey responses from 149 agile developers (1,510 observations), our study uncovers a crucial yet overlooked factor; perceived (in-)congruence between team-enacted and developer-needed agile practices significantly impacts developer well-being. We show that alignment between the use and need of agile practices is associated with higher well-being, whereas mismatches—both excessive and insufficient agile practices—can be detrimental. Interestingly, we find that frequent team feedback seeking amplifies the negative effects of misalignment but does not enhance well-being when alignment is achieved. These findings challenge the assumption that the use of agile practices is inherently beneficial and highlight the need for a tailored, developer-centric approach. For organizations, the key takeaway is clear. A “one-size-fits-all” approach to agile practices can backfire. Instead, fostering alignment through adaptive work environments, flexible agile practice use, and targeted interventions can promote sustainable developer well-being and long-term agile team effectiveness.