Capture the input data
Submit the agreed design or user scenario, environment address, current branch, and acceptance criteria. Check the limitations of the platform, licenses and terms. Grant only the access needed through a separate channel; determine when to revoke access. Collect the client's comments through the agreed person in charge.
Continue with: Website releases: checks, rollback and cache refresh.
Separate implementation and release
Specify who works with production, who prepares the backup, and who checks after publication. Simultaneous changes by multiple developers need to be coordinated through version control and visible release composition. Do not copy the entire old project on top of the working site for the sake of changing one component.
Continue with: Hourly development: estimates, rates and acceptance.
Submit the result along with the checks
Code, changelog, verification method, known limitations, and instructions for required settings are required. If the integration is changed, specify the test scenarios and error behavior. Agree on the estimate for additional requirements before implementing them. This procedure helps the agency to independently accept and further support the result.
Can I start with a small task?
Yes. A strictly limited pilot helps to test the communication process, the quality of the code transfer and the compliance with the expectations of both teams.