5 ms·
My experience is that most retros result in a list of things that should get addressed but never get addressed. Especially because they must be addressed by lar
by maxxxxx 8y ago
My experience is that most retros result in a list of things that should get addressed but never get addressed. Especially because they must be addressed by larger organizational changes once the low hanging fruit has been addressed, In teams where we actually addressed these issues we ran out of things to say in the retro after a few times.
- potatopolis 8y agoThings being recognised and never/rarely acted on is better than them going unrecognised entirely. At least in the former scenario, there's a shared awareness of the problem.
- maxxxxx 8y agoThere isn't. Raising an issue without ever fixing it is very demotivating and causes a "fuck it" attitude.
- pythonaut_16 8y agoEveryone being aware of an issue without it ever being raised or acknowledged is equally demotivating and results in the same attitude.
- maxxxxx 8y agoSame thing. Issues that are known and don't get fixed are demotivating.