It's not a thing in most of the software industry yet. And wherever people do team retrospectives there is a high chance that it is a formal procedure - the onl

It's not a thing in most of the software industry yet. And wherever people do team retrospectives there is a high chance that it is a formal procedure - the only concerns that are voiced aloud are the ones that are known and "approved" by management or are expected to be acknowledged. Any critical concerns that can backfire at a person who raises them are never mentioned, just in case. I'm not saying that all IT companies are like that, far from it, but really the issue is very human one - it is very likely that at least some critical issues are caused by mistakes of the management and unless management can accept blame for own mistakes retrospectives won't really work.