whats the top way scope creep happens on projects?
This was selected as Best Answer I’m going to throw my 2 cents in here. This is a great topic, and anyone who’s spent more than 10 minutes in IT has had to deal with it. I’m not sure all of the responses thus far are really dealing with scope creep. I think most of the responses are talking about the lack of solid Requirements Management processes. Let me explain further. At some point in every project, the development team and the business client have to come to an agreement on what the scope of the project is. Until that point, you can’t have scope creep because you don’t have a baseline scope. Requirements Management, then, is the process used for changing the scope of the project. As long as the process is followed, you won’t have scope creep. That does not mean scope doesn’t change; it means that scope change is managed by an agreed-to process. Scope Creep is then, by definition, any scope that is added to the baseline outside of the Requirements Management Process.
