Scope Creep as a concept is not unique to software development projects but it applies to all industries and areas however it seems that there is always more leeway or more reasons to allow it within software projects. Whenever it does start happening it can easily run away from you and derail the development.
I’ll discuss the different types of Scope Creep that can happen during a development project:
- Lack of Clarity
- Weak Project Manager/Team lead
- Direct communication with the implementation team and client
- Teams adding “more value”
- Teams overpromising
- Lack of stakeholder involvement
- Differing stakeholder opinions
- Late feedback and testing by clients
- Poor Estimates
- Not questioning requests or changes