Governance Process for WordPress Website Deployment
Governance Process for WordPress Website Deployment
Objective:
To ensure that changes pushed to the production environment have been thoroughly tested, reviewed, and approved by the relevant stakeholders.
Roles and Responsibilities
Owner (Rafael)
Approves major changes and new version releases.
Reviews overarching strategy and outcomes.
Project Manager (Renato)
Reviews and approves minor changes, fixes, and updates.
Schedules and greenlights the deployment in collaboration with the Tech Lead
Ensures communication between stakeholders.
Tech Lead (Ryan)
Tests and Reviews all technical aspects of changes.
Coordinates the deployment process.
Provides guidance on best practices and potential impacts.
Webdesigners and Webdevelopers
Responsible for the design elements of changes.
Ensures that design meets project standards before deployment.
Process Steps
Staging Development:
Developers implement changes in the staging environment.
All changes must be accompanied by adequate documentation, including a list of changes to be tested and reviewed by the TL and PM, and any necessary comments in the code.
Initial Testing:
Designated testers conduct initial testing in staging. If the changes were requested by a specific team member, he or she should be included in the testing group.
Tests include functional testing, compatibility checks, and performance assessments.
Any issues identified at this stage should be fixed before proceeding to the next
Review and Approval:
Minor Changes/Fixes:
Submit changes for approval to the Tech Lead and Project Manager.
Major Changes:
Submit changes for approval to the Owner, Tech Lead, and Project Manager.
The Owner must approve any major changes before they can be deployed to production.
Deployment to Production:
Once all approvals are obtained, the changes are pushed from staging to the production environment by the Tech Lead.
A deployment checklist must be followed, which includes:
Backup of the production environment.
Deployment of code and assets.
Database migrations, if applicable.
Verification of configuration settings.
Post-Deployment Testing:
Conduct a smoke test in the production environment to confirm that all features are functioning as expected.
Any issues must be documented and addressed immediately.
Monitoring:
Monitor the production environment for any issues that may arise after deployment for 24-48 hours.
Ensure that all stakeholders are notified in case of any concerns or required major fixes post-deployment, or from any downtime > 1h for any website feature or functionality
Want to print your doc? This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
