This is the Product Owner's job.
The whole point of the product owner is to act as the point of contact between all the stakeholders (including people like someone's boss's boss) and the team itself. In theory, the rest of the team should only ever have to deal with the Product Owner. The Product Owner goes and does all the work of talking to various stakeholders, puts together the stories, and then the team just works on them in order of the set priority, and ignores who requested what. (In practice, it never quite works this way, but close enough.)
However, it is also important to remember what a stakeholder is. A stakeholder is the person who writes the checks. The team gets a list of business requirements, and then fulfills them. Sometimes you get stakeholders who either want something stupid, or who change their mind over and over. That is, unfortunately, their prerogative, after all, the whole point of agile is to let stakeholders change their minds often and to catch stupid decisions faster. Ideally, it is mostly the Product Owner that deals with the stress of all that while the team just takes the stories as they come. Really, the whole point of agile is for stakeholders to determine they don't like something and actually want something different.
Now this is all business requirements. If this boss's boss is mucking about with technical decisions, then, well, you have my sympathy. There is no real Agile term for this other than "not agile". In Agile, the team makes technical decisions, not the stakeholders.
TL;DR - If a stakeholder is overturning business decisions, then this is their prerogative, and it is the Product Owner job to deal with that. If the stakeholder is overturning technical decisions, or overturning any decision mid-sprint, then this is something the Product Owner and Scrum Master should be demanding stop.