I think this sounds like an issue with the change management part of the cycle. It is also a bit of a chicken and egg problem, where agile development has created an environment where changing requirements from customer/user are almost expected, and now we justify those by using agile more and more. Apps also look to implement ever growing numbers of features that no one really cares about, but sound like a good idea in the weekly leadership call.
