> > > the scope must be very narrowly defined or it an run away from you.
This could easily be a topic unto itself. It's very important before you begin a project to have a scope document. I call it a PDG (project development guideline) but you can call it whatever. The most important role of the PDG is to clearly define the scope and detail of the project. Leave no stone unturned and then have the client sign off on it before you begin any work. It can be tedious but it's benefits far, far outweigh the tedium. In my PDG's I include the following: Define all major functional aspects of the project with a brief description of how these requirements will be met. Delivery Date(s). Purpose, Rationale, Mechanics, Key Messages, Dependencies, Format, Reference Materials and finally Tone & Voice of project. Like I said, it may seem tedious but your clients will appreciate your thoroughness and have a clear understanding of what they are getting for their money. The beauty of the PDG is that it actually becomes easier to get a client to pay for changes because they've already signed off on the project scope. Then you create a Scope Change Request document when they want changes. The client signs off on that too. Rinse and repeat. In the end everyone is happier. You know if you've missed anything that's within scope and your client knows what they are paying for. And they don't argue as much when they have to pay for out of scope changes. Sorry for the O.T. but I thought it might be poignant. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:341909 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
