...
- Saying one thing and doing another
- Having a loose/undefined deployment schedule
- Pushing code to LIVE during peak traffic times
- Having only 1 person online/active during the deployment
- Deploying without written signoff
- Deploying without a full backup (Code/DB/Files)
- Deploying on a Friday
Things to Always Do:
- Have a clear deployment plan with step-by-step outline of what needs to happen
- Have a scheduled time or window of time when the deployment will take place
- Have at least one stakeholder online during the deployment (in case there is a need to rollback or update content)
- Get written signoff from the client or PO acknowledging/approving the deployment (schedule and steps)
- Have a QA checklist to run through once the new code is live
- Have a "Content Cut-off Time" after which Content Editors can't update content in the database
- Always run a full back-up before deploying (Code/DB/Files)
- Communicate frequently and often what we are going to launch in the slack channel, with client eyes-on
Steps:
Feel free to use the following checklist as a reference during deployment. You can edit this page, and copy to the project's Deployment Notes doc if you find that helpful.
...