Here we explain how a typical project goes, note this is not a rigid list just an example to illustrate how we usually work.
1. The agency sends us the final assets which includes the design (AI, PSD, XD, Sketch or Figma) and may also include (but doesn’t need to): mobile and tablet designs, a brief and a technical spec.
2. Gooey give a final fixed cost and a deadline, and send over our official quote/spec which breaks down the project and explains clearly what we will deliver. The agency signs and we get cracking.
3. The job is assigned to a Gooey developer and the progress of the job is communicated by our Project Manager. Sometimes agencies like to speak to the developer before project-commencement to talk through the designs etc, this is fine just let us know and we can arrange.
4. Once the developer completes the project, we pass it to our QA team who then check the website against the Gooey spec, the designs and anything else supplied (i.e. your technical spec or brief etc) to ensure the developer has followed correctly. The QA team use BugHerd to log any issues and the developer will then fix and reply to the issues.
5. Once the Gooey QA team is happy with all of our internal amends, the project is handed over to the agency on a password protected white-label domain (i.e. your-project.in-beta.co.uk) where you can review and also log any amends you would like actioning via BugHerd.
6. We give two full rounds of amends, that’s one for the agency, and one for the agency’s client – once done and you are happy, we sign of the project and then either launch the site onto a dev or live environment of your choice (we just need the logins), or we can send the files and DB over.
