If Scope of the project has creeped , this index to what ?

Thank you for invitation..

I'm with an answer of Mr.Rami khatib .

Thank you for the invitation

All the answers are excellent

 The requirements stability index "RSI", are sometimes advocated.

I am not familiar with this term .........

When new features are added to product designs that have already been approved, without providing equivalent increases in budget, time and/or resources

Thanks for Invitation, No any experience about this so Endorse the Experts answer.

In simple words, If scope of the project has creeped, this indicates that the project will be in trouble due to a lack of deploying a well defined project change management system deal with processing any approval or rejection requests.

Scope Creep is typically the result of a poorly defined project. If the starting parameters are incomplete or poorly defined then there is usually way to avoid scope creep.

 

The problem is that the scope is typically defined by the client and the creep is picked up by the contractor. This invariably causes delays that both sides blame on each other.

 

However if you manage the scope creep correctly and clearly define the sections outside of the original parameters the delays can be contained within the creep only and not the whole project as typically happens. 

If the scope has creeped it means that the project is at big risk because it started without a clear or proper scope...it's a domino effect eventually.

Feature creep (sometimes known as requirements creep or scope creep) is a tendency for product or project requirements to increase during development beyond those originally foreseen. Feature creep may be driven by a client's growing "wish list" or by developers themselves as they see opportunity for improving the product. To control feature creep, project management tools, such as the requirements stability index (RSI), are sometimes advocated.

Thanks for invitation I am agree with Mr Ayoub.