Which document is used for post deployment or what is the name of that document.
And what things does this document include?
Software Quality Assurance & Testing Stack Exchange is a question and answer site for software quality control experts, automation engineers, and software testers. It only takes a minute to sign up.Sign up to join this community
It depends on the goal of the document. This could differ per industry/company. Maybe a better question would be: "Examples of post-deployment documentation".
Personally I see no need for any post-deployment documentation. Most documentation can be produced before deployment, for example, the changelog which informs users what changes where deployed.
Working software over comprehensive documentation
That is, while there is value in the items on the right, we value the items on the left more.
Challenge yourself and your teams if you really need more documentation. Who benefits from the post-deployment documentation? How often would they really use it? Could an email to key stakeholders be enough? Something like: "Deployment was complete, smoke tests successful, the system is operational with the new version. See the changelog here.".
A mandatory process that any software testing company should follow is to provide Sanity Report and Release Notes to the client and stakeholders post-deployment on the live environment.
Sanity report should have information regarding if the list of changes is successfully deployed or not. It should also document any changes that were planned but were missed.
Release notes should include the below details.