How do you handle scope creep in Scrum?

Short answer: In Scrum, scope creep is managed by controlling what goes into a Sprint — not by freezing the entire project.

Explain a bit more

How it’s handled: Sprint scope is locked once planning ends. No changes mid-Sprint without discussion and agreement. Product Backlog remains flexible, so new ideas or requirements are added there — not injected into the current Sprint. The Product Owner (PO) decides what gets prioritized for future Sprints. Example: If a stakeholder requests a new login method during the Sprint, the PO thanks them, adds it to the Product Backlog, and it’s considered in the next planning session — not immediately worked on. Follow On:

Real-world example (ShopNest)

Agile for ShopNest means ship a thin checkout slice every sprint, get feedback, then improve—not a 6-month big-bang release.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.