When scrum is new, everybody seems to enjoy it but after repeated routine of sprints, planning, and daily reviews it becomes in interesting and old. There are some early signs or indicators which can prevent this kind of situation:

1.       Repeated

2.       Unresolved issues in retrospectives

3.       Stories are not demonstrable;

4.       Unfinished stories are split and carried over the next sprint

5.       During sprint planning, tasks are assigned to team members

6.       Team members are not 100% on the project or are withdrawn from the project.

Read the complete article here: https://www.scrumalliance.org/community/articles/2016/may/when-scrum-becomes-stale-the-team-under-performs

Agile teams must embrace change. After all, that is what agile means, right? Accommodating changing customer's requirement… But the stakeholders or customers must also understand that nothing comes for free in the world. So are changes. They have a cost related to them. Scrum works on a rule that once the required changes are fully stated, a sprint begins. And no changes are allowed into a sprint. Once a sprint is started, it’s not disturbed and the team’s entire focus is on selected work. This is good and works efficiently, but can sometimes backfire. The customer can question that the foundation of being agile is to welcome changing requirements. Well, yes, but they aren’t free. Customers must understand that changes introduced beyond a certain point have a cost related to them. And both the customers and organization should work together to optimize results with the minimum cost.To know more, read the article by Mike Cohn (founder of Mountain Goat Software), at: https://www.mountaingoatsoftware.com/blog/change-isnt-free