What are best ways to avoid Scope Creep?

What are best ways to avoid Scope Creep? Can you please discuss this when you said: "Creeping user requirements contribute to overruns and degrade product quality", when you higlighted the risks from inadequate requirements process. Also what you meant by "Requiremt Menegement"? Please explain breifly.

Scope creep means changing scope. The best way to avoid scope creep is better requirement engineering and trequirement verification from user before moving forward.That is, requirements must be correct, complete, feasible, unambiguous, prioritized and verifiable.

Meaning of “Creeping user requirements contribute to overruns and degrade product quality" is that identifying and adding new requirements to the list at some advanced stages (Design, development, testing etc) will not only cause project to be overrun in terms of time and money but also quality of product will be degraded as later added requirements are not well mapped with whole system. Addition of new requirements later also mean requirement engineering was inadequate that can lead to adding some unnecessary requirement and missing some core requirement affecting the overall quality of product.

Requirement management is to manage requirements from every perspective. That is, along with requirements there should be some way to manage requirements if they change, increase or decrease by identifying their associated risks.