How to manage requirement change in Sprint?
Can you please be more specific?
Describe the situation you are in.
Is it only a detail or is the Sprint Goal affected?
Want to understand that should we accept change during the sprint execution and how to deal it if any requirement change in story as SM?
During the Sprint:
•No changes are made that would endanger the Sprint Goal;
Only the Development Team can change its Sprint Backlog during a Sprint. The Sprint Backlog is a highly visible, real-time picture of the work that the Development Team plans to accomplish during the Sprint, and it belongs solely to the Development Team.
This means: Yes we as SM can accept change as long as the Sprint Goal is not affected and the DT and PO agree on it.
Whats your situation/context Sushil?
Does the team have a Definition of Ready in place which allows the team to express the required quality of the user stories and supporting documents before committing to a sprint goal?
This should help reduce this "change" behaviour, rework and back and forth communication during the sprint timebox and help the team commit to a clear and unambiguous sprint goal at sprint planning.