Operational Acceptance Testing and Release Management

Before releasing things into the “wild” I’d like to think we’ve done some planning, risk assessment, backup contingency/recovery plan, hopefully some availability and capacity management to test reliability, also may be some training would be nice and most importantly does it pass the customer and user acceptance as fit for use and fit for purpose to meet business needs.

Wouldn’t it be nice to do these things even before release? Do a bit of forward thinking and actually liaise with stakeholders and the business to make sure the “system” works. Project Teams may even be able to reach up and get their dusty PRINCE2 manual of the shelf too.

Another thing that would be very helpful would be some communication, a dialog between the business and IT might be beneficial for delivering things they what and are practical and usable. Dare I even say “add value”?

In a nutshell quality management, monitoring, software testing will help you deliver customer acceptance and customer joy. Managing complex system is made easier by mapping the inter-dependencies between people, processes, products and partners. That’s what makes any system distribute quality and value.

Before and after release monitor metrics than identify service improvements for Version 2 and repeat OAT again. Remember costs don’t stop at the end of the project – ongoing support and operational cost need to be factored in.

Unless you want to keep trying to fit squares in to round holes I suggest Operational Acceptance Testing is factored in to your Release Management or you may find the whole project drops in to a hole.