There’s an interesting article over on Six Revisions on Feature Creep. It’s worth a read if you’re a project manager, because almost everything there translates directly to scope creep for projects. It talks about some basic things:
1. Scope creep will happen. It’s natural and not the end of the world. You must manage it. If you don’t have scope creep, either you spent too long analyzing your project in the beginning (and you can spend too much), no one cares about your project and isn’t paying attention, or there’s something else wrong. No one has perfect scope and requirements at the beginning.
2. Allow enough time to gather requirements- make sure there’s time in your project to acknowledge and handle the scope creep.
3. Set boundaries. There can only be so much creep.
4. Don’t be afraid to push back.
5. Keep focus on the task at hand.
6. Trust the experts as much as the client.
7. Do your homework before you okay a piece of scope creep.
8. Keep control on your own scope creep as much as the customer’s.
I could write a ton on all of these topics (and I might later), but I think you’ll get the gist from Six Revision’s article. Take a look!