I argue that's actually a misconception of many scrum practitioners. It's not really "get feedback often", it's "get feedback early". "Often" is just a bad approximation of that. The difference is most obvious with retrospectives - if you just do them often they feel like a burden. What you want is to get early opportunities to improve .... but that's not necessarily through a very frequent retrospective! You have to let things crystallize a bit, so that people can observe the effect of process changes & give accurate+reasonable feedback on it.

That's... actually pretty accurate? Dang.

So it becomes this?

* Get feedback often from the business owners

* Get feedback often from the developers

* Get feedback often from the users

And act on that feedback.