Agile is a fancy word for we, the top Dawgs can change the requirements at any time and you dev peasants will have to deal with it.

If it changes anytime it’s not agile, it’s a mess.

@drtokky This

It's supposed to be changed in iterations! That's what Sprints are... You're supposed to do a Sprint of work and then you evaluate where you are, what you can improve, what changed since the start and what the next sprint should be...

Essentially a good Agile implementation is like doing function fitting but with people!

Actually in agile there are no 'top dawgs'. Unless you are referring to users who are requesting changes but even then a Product Owner should be vetting those requests, figuring out the details, then bringing them to the team for refinement and sprint planning.

The problem is when top Dawgs actually DO influence things around the correct methods. This is where the problems begins and I experience it way too often :(

The requirements are the reason you write code. If they change - there's no reason for you to continue what you were doing.