By TonyV on
I've learned over the years that project management is almost as important as hardcore technical skills when it comes to finishing a website. Scope creep and clients constantly dragging their feet and/or changing their minds is an ongoing problem.
I'm curious to hear from this great community what techniques and tools you use to manage the client, the project, and eliminate scope creep.
Thanks for any and all ideas!
Tony
Comments
I tend to get things on
I tend to get things on writing on what I will deliver. Formality of that depends on the size of the project but it boils down to be able to "point" to something and say that is not in scope and if you would like I can add it but it will add X hours to the estimate.
I agree with nevets. Having
I agree with nevets. Having everything down in writing is a great way to track your own progress and to ensure that there isn't any room for scope creep. We follow an agile method, so the client is always in the loop on the status of things and if something arises to threaten the timeline, its communicated immediately.
As for tools, we use Redmine and Google Docs extensively. They're great for PM (and the devs love them too). Here's our blog post on the topic: http://evolvingweb.ca/story/agile-project-management-google-docs-git-and....
As a project manager I
As a project manager I constantly deal with this problem -- there is not any one way to control scope creep, how bad it hits you depends a lot on the client and your working relationship with them.
I have found, in general, the best method is to make sure that the project is scoped out as much as possible before you agree on anything in writing -- make sure EVERYTHING you may have to do is included in the bid/agreement. After that -- anything added to the scope must be amended and priced.
On some of the larger projects this process is not quite as easy, but for relatively small-medium sized websites the best way to combat scope creep is to be inordinately clear on what SCOPE is.