Recurring opinions or productive improvements — what agile teams actually discuss in retrospectives
An 3-years analysis of a team's retrospectives, with dire conclusions: people keep forgetting what they already learned, keep discussing unsolveable problems out of their control, and keep debating opinions based on biased interpretations or incorrect understandings.
- from
- Engineering Team Management
- added
- 2026-10-10
- likes
- 0
similar
-
-
An Alternative Approach to Re-Orgs At Your Company caseyaccidental.com
“Trying not to repeat re-org mistakes, we started working on a structure that would make the re-org act like a feedback-fueled progress driven by the teams instead of by people above them.” This is an attempt to extract from the ground up signals pointing to inadequate…
-
Technical debt as a lack of understanding daverupert.com
“The problem lies in "never reorganizing (the code) to reflect your understanding." (…) Organizationally, you pay in velocity and turnover; talented people are going to leave after a few rounds of bullshit.”
-
Learn out of mistakes. Postmortems to the rescue. fernandocejas.com
-
How do managers get stuck? elidedbranches.com
Identify scenario preventing managers to be promoted at the next level.
-
The failure of Scaling Etsy archive.ph
When a company lacks technical leadership: developers waste time in costly refactors, over-engineered systems, and ends up detached from the business and product.
Engineering Team Management › Agile: “An 3-years analysis of a team's retrospectives, with dire conclusions: people keep forgetting what they already learned, keep discussing unsolveable problems out of their control, and keep debating opinions based on biased interpretations or incorrect understandings.”