client checklist

Checklist of things that a perspective client should provide to the developer:

• Budget for the project. It will help the developer to determine what can be realistically achieved for the money and propose a list of possible options.
• A complete list of coding/design requirements. Without such a list, it will be impossible complete the project on time or even to come up with a realistic timeline. If the client doesn't have a good idea what he or she wants before the development stage starts, the developer will do a lot of unnecessary work at best or completely fail to satisfy the client at worst.
• A clear outline why the work is necessary and what the client expects to achieve. It is often the case that from the point of the developer, the client's requirements do not correspond to the client's goals. It is up to the developer handle the inconsistencies between initial requirements and actual goals. In most cases, implementation details are the developer's concern, not the client's. Example Client: We need to create and set up a mailing list for our users. Developer: Ok. May I ask why you need a mailing list? Client: We would like to keep our users informed about website updates. At this point it would be wise for the developer to propose to add an RSS feed to the website instead of full-fledged mailing list.
• A deadline. If the client doesn't have a set deadline, the developer and the client should agree on one.
• If a project is supposed to be built on top of or add to an existing codebase, access to the source code and data. In order to estimate the cost realistically and avoid unpleasant surprises, the developer needs to have a clear understanding what he or she will be working with.

References

Design checklist: What clients should provide their designer