Did you enjoy the problems then!

Today I had a planning day that’s not to say that I didn’t actually do anything, I covered a few things off on the work schedule – mostly scripting stuff for the capacity planners. I have been looking at the work that we’ll have to do in the quite near future in respect of the steaming pile of Poo that our relocation manager (Slinky) left behind, It’ll all have to be sorted out before the project goes much further, this will involve rebuilding several servers and relocating a slack hand full of containers to other servers for the duration of the work. Now this work is a direct result of the first set of builds not being done correctly, the reason for this is that we were put under a lot of pressure by Slinky and his mate BIC – neither of whom had a clue. And when things started rolling at a reasonable pace the relocation manager (Slinky) bailed out, leaving a significant mess behind him – one that will have to be sorted out very soon if there is to be any hope of getting this project back on track. Getting the project back on track will involve a quick rebuild of several of the MX000 servers, unfortunately some of these now have live apps on them and the slot where we do the work will have to be carefully planned.

How could this happen I hear you say, well when the project manager delivers the project plan several months into the project. And when you’ve been told that this is the way we have to build the servers, only to find out that this isn’t how we have to build the servers – you seem to be set back a bit. This spurred of a mini project, deciding the baseline build! Yes I know that this should have been decided before a single server was built, but due to pressure applied  and incorrect information supplied by Slinky and BIC this didn’t happen. Still Slinky buggered off at the earliest opportunity, no great loss I’d say – in fact he’s taken the money under what to me mounts to false pretenses I’d even go as far as to say he’d committed cash and carry!