For Webmasters
Detailed Project Description
Your project description should be as detailed as possible. It's better to have too much information than too little. Some people choose to summarize the project in the description field, and attach a file with more detailed info (for interested bidders). Which is a good idea. Remember that you can only attach one file so if you have a drawing, project details, and a non-disclosure agreement, they should all be contained in one file.
Additional Features
If you have additional features you would like in your project, which you did not mention in the project description, please tell the Programmer BEFORE they begin work.
Request Proof
Before you pay for the project, you should ask the Programmer for proof of functionality and compliance to your requirements. Once you accept a project, it is too late to cancel, and you will be expected to pay for the service.
Payment Method
Before the work begins, you should discuss with the Programmer how you will send payment.
|
For Programmers
Know The Project
You should know how you will approach the project before you place your bid. If you need more details, post on the message board for that project, request more information from the Webmaster. If you don't, at least make sure you are clear about the project before you begin working on it.
Updates
You might consider updating the Webmaster on your progress throughout your work, especially if it's a long project. This will assure that there is no confusion over how the project is suppose to be when you finish it.
Provide Proof
Before requesting payment for a project, you should offer to provide some form of proof of functionality and compliance to the Webmasters requirements so that they can confirm it is what they wanted. You are almost guaranteed satisfaction if you do this, because the Webmaster can confirm your work before they receive it and pay you.
Payment Method
Before the work begins, you should discuss with the Webmaster how you want them to send your payment later on.
|
