Document opportunities as they are found throughout the review. You will most likely find yourself referencing all sorts of documentation both internal and external in the review. Recording the links to those docs can be very helpful for anyone working on the changes after the review or who wants to understand why a certain recommendation was made.
Review available opportunities and prioritize them based the goal of the review. Implement changes in batches to see the impact of individual changes and make troubleshooting easier.
Test changes made by running a pipeline. After confirming the changes work on a dev branch, be sure to test them in different environments as well. Compare the new pipeline metrics to the metrics recorded in the config review to confirm changes were successful.
It is beneficial to monitor the changes after releasing them to confirm metrics don’t start going in the wrong direction unexpectedly.
Record the test results, even if they didn’t work, to help future config reviewers or maintainers to understand why certain features or functionality do and do not work in the project.
Previous Step: Project Settings
📑 Table of Contents
- Configuration Review Preparation
- Review Each Job for Improvement Opportunities
- Review Each Workflow for Improvement Opportunities
- High Level Improvement Opportunities
- Finalize Review