I’d be interested to read a similar post and how the specifics change in the virtual team/multiple provider environment?

I completely agree on the Gluttony sin.

Saying no to clients can be very difficult, especially if the changes start off small and then become more complicated and start to have an impact overall.

As the project manager, if you are organised and respond clearly to the client then you can let them make the decision as to whether you incorporate changes (at additional cost and a change to the timescales) or not.

A good tactic can be to put changes into a ‘Phase 2′, as was mentioned in the article, so you can concentrate on delivering the first phase on time and on budget, as long as you can convince the client that what they are asking to change is outside of the original project scope.

Cool article, enjoyed it from first to last sentence. I think there are a few webapps that help us manage efficiently web projects, no pride involved (just time tracking), no need to be greedy either… but I do feel that Lust is not so bad after all. Creatives all around the web need it or at least I need it. Otherwise it would be a big waste of ideas, sleepless nights and caffeine. But I see your points, though!

Thanks for your comment. Glad you agree :) I have also been introduced to your articles and posts too so it is nice to meet a like-minded soul.

Quality not quantity I guess. I agree! It’s easy to spread yourself too thinly and then actually fail to deliver across the board.

Rob.

Scope creep is a battle I face most days! The confidence to say no is definitely a good tool for Project Managers to have and it is usually for the good of the project too.

Rob.

Good point. It’s hard to keep detached sometimes though isn’t it but you are right, keeping some sort of distance does help numb the pain :)

I wasn’t aware of Sam’s articles so I will definitely check those out too :)

Thanks.

Rob.

thanks a lot!

http://www.thesambarnes.com/web-project-management/web-project-management-seven-deadly-sins-part-1/

Personally I think the best way of avoiding this is by being very clear about project scope right from the initial briefing stage, especially clarifying any areas where you think there can be potential points of confusion.

At the same time it’s also good to deliver a project above-expectation… Just not too far above!

Try not to get too emotionally attached to any work that you do, because it is bound to be changed, overhauled, ripped apart, put back together, etc. That’s not to say that you shouldn’t take pride in what you do and get into it, but If you design and/or build with this in mind, when the changes come, it won’t hit you over the head as hard in the end.