The success of any project can usually be determined by the success of the project specification. Every project needs a specification to define the scope and objectives of the project. So, what makes a good project specification?

If you don?t ask good questions, you won?t get good answers, and this is most definitely the case with project objectives. Every good project specification will start by stating clearly defined project objectives; these are key to a designer or developer understanding your requirements. The objectives having been defined, the designer or developer will proceed to produce a written specification, clearly stating how the solution will be achieved.

A good specification should clearly define the scope of a project, ie, what the solution (be it a Web site, or piece of software) will do, and in some cases what the solution won?t do. This will ensure that both the designer / developer and the client understand the scope of the project from day one and will leave no room for interpretation on how objectives will be achieved.

Project timescales and milestones should also be highlighted in any good specification, as should payment schedules and payment terms. A client will need to know when to expect delivery of a project milestone, and when the project is due for completion.

Finally, it is key that both parties understand the contents of a specification. A technical specification will by default contain technical references, abbreviations and terms that are not fully understood by a non-technical client. A good specification should be, whilst technically sound, written for the target audience.

There are several approaches and methodologies to the project lifecycle, however, the successful ones will all have one thing in common, clearly defined project requirements.