So been busting my hump all week, working long days and long nights to get the current release of the system massaged through to UAT sign off.
As the system testing is piss weak, I have implemented a new "Pre UAT" phase which is wholly and soley me and is an attempt at squeezing out issues before UAT so at least we can say we know about them.
Until today. The whole UAT was a failure. And the reason?
The development, integration, pre prod and live environments are all on different versions of the software. Different versions of JBOSS, MySQL, patch levels. Horrible.
And to cap it all, the code has financial aspects to it with a month end process. So if the financial process fails during UAT it is a one shot gun. There is no way of rolling back and going again.
Just spent an hour explaining simple configuration management, snapshots of virtual machines, change management procedures.
Will they listen? We'll see.
It's just a shame to see a team collectively try so hard and still come wide of the mark time and time again.
This is why I have been a grumpy fracker all week.
As the system testing is piss weak, I have implemented a new "Pre UAT" phase which is wholly and soley me and is an attempt at squeezing out issues before UAT so at least we can say we know about them.
Until today. The whole UAT was a failure. And the reason?
The development, integration, pre prod and live environments are all on different versions of the software. Different versions of JBOSS, MySQL, patch levels. Horrible.
And to cap it all, the code has financial aspects to it with a month end process. So if the financial process fails during UAT it is a one shot gun. There is no way of rolling back and going again.
Just spent an hour explaining simple configuration management, snapshots of virtual machines, change management procedures.
Will they listen? We'll see.
It's just a shame to see a team collectively try so hard and still come wide of the mark time and time again.
This is why I have been a grumpy fracker all week.
Comment