I think the question is fundamentally flawed. Agile is meant to embrace change, even late in the game. The idea is that the scope becomes flexible, while you have a fixed schedule and budget. When one or both of these expires, it's an opportunity to re-evaluate any work remaining and to decide whether to continue investing or stop and accept what has already been delivered.

Let's explore strategies that can prevent scope creep. Clearly Define the Scope. ... Ask About Changes Early. ... Obtain Formal Sign-off. ... Maintain Ongoing Scope Communication. ... Implement a Change Process. ... Confidently Reject Out-of-Scope Requests. ... Involve Stakeholders. ... Assess Risks Thoroughly.

Having a robust change management process can help in controlling the scope change. Hear are some technique 1. Capture the Changes 2. Plan how we can bring the changes in the system 3. Communicate properly to all involved party.

No such thing as scope creep in Agile projects. Only thing that can't change is the scope of the iteration and if that has to change, stop the iteration and start again. If you don't do this team predictability is lost

To manage scope creep in Agile, keep the project scope clear and regularly review the backlog. Evaluate new requests against the project’s goals and discuss their impact. Ensure all changes are agreed upon before being added to the scope. This keeps the project on track.