Yeah, that's fair. I guess "Effective retros are essential" would be more accurate. It's just like any other step of the process: if the retro isn't working, figure out a different way to get the feedback. Nothing needs to be set in stone. You pick a starting point (i.e. Scrum + Retros) and make changes until things work as well as you need them to.