The point of Agile is to give power to the team and also to use The Process to protect them from ad-hoc management interference during sprint.
10 The stakeholder says which features are the most important and gives the team a prioritised list.
20 The team goes through the list and determines how much work each will take. At this point the stakeholder might be asked to re-prioritise.
30 Team picks tasks from the top of the list for each sprint and shows the result to the stakeholder after the sprint in a demo.
GOTO 10
That's it.
If someone from outside the team has "a quick request" that needs to be done ASAP, the scrum master shows them the prioritised list and asks them what features should be dropped. If the someone is stupid enough to pick something, they can go wrestle with the stakeholder(s) of the deprioritised tasks about whose thing is more important.
The team doesn't see anything of said quick request, they can focus on their sprint.
If the stakeholder has any "quick requests" The Process says all work for the sprint is to be scrapped (no one really does it, but you don't tell that to the customer) and the sprint is restarted with the "quick request" included. In my 20 years in the business, zero customers have taken the "scrap the sprint" route.
But none of this will work unless an expensive enough consultant can convince the higher ups that it's a good idea. If they're not with the process, you get scrumfalls, 45 minute standups and other crap.
10 The stakeholder says which features are the most important and gives the team a prioritised list.
20 The team goes through the list and determines how much work each will take. At this point the stakeholder might be asked to re-prioritise.
30 Team picks tasks from the top of the list for each sprint and shows the result to the stakeholder after the sprint in a demo.
GOTO 10
That's it.
If someone from outside the team has "a quick request" that needs to be done ASAP, the scrum master shows them the prioritised list and asks them what features should be dropped. If the someone is stupid enough to pick something, they can go wrestle with the stakeholder(s) of the deprioritised tasks about whose thing is more important.
The team doesn't see anything of said quick request, they can focus on their sprint.
If the stakeholder has any "quick requests" The Process says all work for the sprint is to be scrapped (no one really does it, but you don't tell that to the customer) and the sprint is restarted with the "quick request" included. In my 20 years in the business, zero customers have taken the "scrap the sprint" route.
But none of this will work unless an expensive enough consultant can convince the higher ups that it's a good idea. If they're not with the process, you get scrumfalls, 45 minute standups and other crap.