Create an Process for Testing and Peer Review for all CMS Work

[gracekretschmer-metrostar]

User Story or Problem Statement

As a member of the CMS team, I need to understand what is expected for me when I push out changes to CMS for testing and peer review.

As an editor and veteran, I need to have confidence that Drupal CMS and content on VA.gov will be consistent and stable and, in turn, not negatively impacted when there are changes to Drupal CMS.

Description or Additional Context

This work is an outcome of this retro: https://easyretro.io/publicboard/Jt2NFeJSj3ccjRFY0DuStNd6Gnk2/3a5f48b1-5650-4ff5-a6df-756450452cb9

Steps for Implementation

• Create a standard process for all changes and always follow the rules of that process.
• Every ticket should have a test plan.
• Crete process for peer review process and stick to that process

Acceptance Criteria

• [ ] The CMS team has an understanding of what is expected for them when they make changes, both with a test plan and with peer review.