Developer handshake

[Chris Gallon]

What documentation do you recommend we gather from Developers when they deploy changes to our environment so we can provide ongoing support in BAU

[Donny Techiera]

Change Request Details
Business justification for the change
Scope and impact analysis
Deployment timeline and rollback procedures

Technical Implementation Details
Description of code changes workflows or configuration updates
Updated scripts UI policies business rules and integrations
Database schema modifications including tables fields and relationships

Testing and Validation Documentation
Unit and functional test results
User acceptance test sign off and stakeholder approvals
Known issues and resolution steps

Security and Compliance Information
Access control modifications
Data privacy considerations and encryption practices
Audit logs and traceability of changes

Performance and Monitoring Metrics
Impact on system performance and load times
Required adjustments to monitoring dashboards or alerts
Backup and recovery plans

Training and Knowledge Transfer
Step by step guides for administrators
End user documentation for feature changes
Troubleshooting procedures

Having this documentation readily available helps ensure operational efficiency rapid issue resolution and long term governance.

[Dr Atul G- LNG]

Hi @Chris Gallon 

Mainly, it is a change record only. I assume in the change you linked the stories as well, and that story might contain the technical document for the particular request. It is equally important for you, as the change/release manager, to maintain a kind of knowledge article where all changes going live in production are documented.

For BAU, a high-level or low-level design, templates, and Excel sheets used during implementation should also be shared.