Only accepted work is recordedAboutGuidesContactSign in
CitePepCitePep
Running Agile Retrospectives for Continuous Improvement
Correction Project Management

Running Agile Retrospectives for Continuous Improvement

Corrected by Emir Baycan · on When Notes Fly · 15 November 2026 · View published page ↗

How to run a retrospective: one that surfaces problems without changing anything is actively corrosive to morale.

Needs stronger evidence

The exact change

Before
A 2021 study by Cizek and colleagues in the Journal of Applied Psychology found that remote teams with explicit structured communication protocols (defined turn-taking, explicit time-boxing, and required participation signals such as thumbs up/down reactions) significantly outperformed teams using unstructured remote discussion on both participation equity and decision quality. | These protocols matter more in retrospectives than in almost any other meeting type, because the retrospective's value depends on all voices being heard.
After
Removed. | Removed.

Suggested change

Removed 2 unsourced claims.

Why this is better

Each study and survey figure in the article was checked against the published source. Claims for which no published source could be located were removed.

More by Emir Baycan in Project Management

All of Emir Baycan's contributions →