3 ms·

I've seen many people complain about reviews and retrospectives in those threads... But they don't seem like a bad thing to me. The problem is if the sprint is

I've seen many people complain about reviews and retrospectives in those threads... But they don't seem like a bad thing to me. The problem is if the sprint is too short. But if the review and retro are done e.g. once every month or so, it can be a good way to see what the other teams have been doing and get an overall picture of your software. And the retro can be a good opportunity to talk about any problems that you encountered, and maybe trigger a solution, or at least just vent about it.

re-thc 3y ago
The problem is nothing comes out of it. We run retros and there are action items and they go into a black hole. The higher ups do it to follow the process and not to fix the actual problems. It gets tiring after a while of time wasting.
watwut 3y ago
I do not want to talk about these problems again and again and again. I would like to see some improvements. First few times it works as a psychohygiene, but then it just becomes annoying. So teams stops talking about actual deep issues on those meetings and they are are creating an illusion of happiness.