Good succinct list, although I must admit I'd add another paragraph right at the beginning about backups - taking fresh ones and/or verifying existing ones, perhaps also performing a test restore or two. My modus operandi has always been to have a fallback position, and, if none is forthcoming, to create one, so knowing I've got good backups from the point I started is perhaps number one on my list.
A while ago, I read a similar article regarding Oracle DBAs, but this time it was what to do when one is about to leave. One of the suggestions was to ensure, if possible, that all important databases were restarted a significant amount of time BEFORE the incumbent DBA left the building for the last time. The idea was to avoid hidden time bombs of changes that have been applied that are still to come into force (running parameters vs configured values, for instance). It also ensures problems are seen whilst the person with the knowledge of the system is still around to fix it. Coming back to Daryl's article, I'd still suggest it's a good idea to follow up taking your backups with a plan of rebooting all servers as soon after you've started as possible so that the environment is in a known state.
Semper in excretia, sumus solum profundum variat