It doesn’t take long on any project, regardless of genre, to be introduced to scope creep. It is an inherent aspect of IT development. Call it scope creep, requirements creep, call it whatever you want, it is added features or uncontrolled changes that are outside the scope of a project. Scope creep comes about so easily and also, so elusively. A simple discussion about the “what ifs” and before you know it the project scope has expanded beyond the original objectives. The problem with Scope Creep is, as new functionality is added; nothing else gets adjusted, such as funding or schedule. 

Scope creep can be the result of one or several common scenarios.

According to a recent post on the Windows Team Blog, "the United States has joined the ranks of Austria, Poland, Sweden, Denmark, Finland and Norway in dropping below 1% usage of IE6" (emphasis mine). Global usage is at 7.7%, mainly due to its widespread use in China (25%).