Almost everything in Scrum can be seen as protecting the team.
ONE example (there are many):
Problem: vague requirements
Solutions in Scrum:
Acceptance criteria on stories need to be clear
whole team grooms the story, everyone understands it and does planning poker to agree on costs. If the team doesn’t all understand it, it doesn’t get past this point
only fully groomed stories get into a Sprint and get worked on.
EVEN IF YOU GOT IT WRONG, you demo what you did every sprint, and the stakeholders can ask for additional work in a future story, reducing the cost of getting it wrong once.
Why?
Almost everything in Scrum can be seen as protecting the team.
ONE example (there are many):
Problem: vague requirements
Solutions in Scrum: