Why Suppressing Conflict Hurts Agile Teams, and a Four-Step Approach to Managing It
An article on DEV Community argues that disagreement during Agile work, such as debates over code reviews or sprint commitments, is a normal and useful sign of engagement rather than a failure. It warns that leaders who rush to smooth over friction push tensions underground, where they breed resentment and apathy. The piece describes how unaddressed conflict erodes psychological safety, stalls decisions, and hides technical debt. It recommends separating ideas from personal identity by focusing on systemic goals and surfacing silent disagreements through anonymous retrospectives and targeted one-on-one questions.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in