Tootfinder

Good code release at work and zero issues! People don't see all the work done in the background weeks before.
Multiple walkthroughs with some of the clients, testers, developers, and the support team. The full set of instructions, modules, db changes, job changes, and schedule changes are reviewed. The day of the release, the support team and release coordinator (me) walk through every job that implements the release, special jobs, backups, and checkpoints.
When done, we d…

Never too many walkthroughs for a release. It may be a bit of overkill, but it works for us...
1. Pre-release the day before to go over the schedule of activities and assignments.
2. Schedule release and related backups.
3. Day of release and after schedule created for run another walkthrough to verify that the backups are where they need to be, checkpoints are there, start of the process is on manual hold.
4. Schedule an open teams call for the leads, devs and supp…