Best Practice: TDX / Solution Delivery Review of postChangeIssues Tag

Statement of Best Practice

• Occasionally, changes implemented in the production environment have unintended consequences or side effects. When this occurs, the change ticket and any resulting incident tickets must be tagged with postChangeIssues. A group will review the tagged changes for any continuous improvement opportunities for our processes, documentation, or general knowledge. The group will be comprised of members of Solution Delivery, IT Process and Planning, and anyone else who is interested in contributing to the process

Reason for Best Practice

• Solution Delivery wants to standardize a process for evaluating tickets tagged following the Change Advisory Board processes

Entities Affected by Best Practice

• Solution Delivery staff

Responsibilities

• Solution Delivery PostChangeIssues RACI Chart

Best Practice

1. A group of members from Solution Delivery teams will meet quarterly to review the quarters' change tickets that have been tagged with postChangeIssues
2. The group will run postChangeIssues report in TeamDynamix
3. The group will review all changes and tickets tagged and save the results in postChangeIssues Review Data in a new tab
   1. The tab should be named for the month and year of the review
4. The group will compare the review with previous months to look for trends and similarities on things going well and opportunities for improvement
5. The group will write up any recommendations for improvements and adjustments to Sol Del processes, documentation, or otherwise identified procedures to present to the appropriate owner
6. The group will out relevant information to Solution Delivery as appropriate during the Solution Delivery All Staff meeting

Related Documents, Forms, and Tools 

• postChangeIssues Review Data 
• PostChangeissues Review Documents Google Drive

Revision History

• 01/30/2025: Process Written