On the latest In the Trenches, Kevin was talking about using checklists, especially when working on a number of machines at once. This weekend was a perfect example of another good reason to have checklists. We were rolling out software upgrades by rolling out a new desktop image to about 120 desktops. This, unfortunately, required us to go around to each machine, run some scripts, run the build, reboot, run some more scripts, reboot, configure the software, etc. We each took around 11-12 machines, were given the checklist for those machines and went on our way.
It was great to be able to leave the checklist with the machine as you bounced from machine to machine starting the build, coming back to finish, etc. It was even better, when I was able to get my allotment of machines done early and went to help out some folks who ran into problems and got delayed, to be able to sit down at a machine they had been working on and know exactly where they were in the process.
I have to give credit to the folks running this project, that was a great idea!
Follow these topics: Tech