This is a good place to start but you also need to commit to automating these steps. Copying and pasting URLs is a waste of time, rollbacks should be automatic, contributor lists should be auto-generated etc. Since it takes time to automate each new thing a checklist is still a good idea, but you have to recognize the danger of engineers subverting/rejecting the process if you let the list grow much at all.
Agreed. At my job we've integrated all the tools. Developers have to put the ticket number in the commit manually, but then the tooling will attach the commit to the ticket automatically. There's also a bot that checks what you're committing and adds checklists for riskier things.
Then the ticket is picked up on merge to master which creates a change list. Everything gets deployed to QA where it's tested. QAs go over the changes and approve it, then developers push to production. Afterwards a random developer from a different team is picked to do a post-deploy review which spreads knowledge and sometimes picks up other changes.
