3 ms·

> Doing retrospectives once in a while to slow down and look back. Managers and leaders should talk the least in such retros. Encouraging feedback sessions with

> Doing retrospectives once in a while to slow down and look back. Managers and leaders should talk the least in such retros. Encouraging feedback sessions within team. And act upon them. I have sat through so many retros which turned out to mostly be about writing a report. Now, retros are something I try to get done as quickly as possible.

NAHWheatCracker 5y ago
Every time I join a new team, I get my hopes up for retrospectives. I contribute ideas about how we can improve how we work for the first few months. Then I realize that my suggestions are ignored and "action items" never have follow up. I revert to contributing nearly nothing. I usually come up with a "what we did better" item so that I don't appear completely disengaged from the process.
- afarrell 5y ago
  Retros which don’t occasionally produce items of investment work that flow into the team’s regular cadence are anemic.
- quonn 5y ago
  It would be better to do retros rarely or whenever requested (when there is a need). But that‘s not what Agile suggests.