Integrate change management processes to accommodate new automations before production implementation. Don't accomplish this task and be prepared for the classic "two steps forward / one step back" problem. You will be stuck with automations breaking down upon inevitable environment changes.
* Run. OK, you've exercised your muscles and have a success under your belt. It's time to stretch. Extend automation initiatives to new applications - one-by-one. Over time, implementing multiple processes or linking them together is do-able. Beware of moving too hastily, before securing some solid wins. Once, you've got a few under your belt, let 'er rip!
Tackling ITPA infrastructures according to these basic guidelines has proven successful for a number of companies. The tips sound simple, but it's surprising how many knowledgeable enterprise IT organizations miss them and suffer the consequences of rework, delays, process breakdowns, and more.
IT automation doesn't have to suck. It doesn't have to cost an arm and a leg or put anything in a sling! You might want to try Automation as a Service or some of these other tips to protect your "AaaSets."
# # #
About the author:
Prior to joining Appnomic Systems, Mr. Solnik was the president & COO of OpSource (a Silicon Valley Infrastructure as a Service (IaaS) company recently acquired by Dimension Data, a $6 billion global systems integrator) where he was responsible for the operations of over 200 web applications including some of the most successful SaaS and software apps in the world. His customers relied on him and the OpSource team to ensure their applications were performing well - 24x365. After spending a number of Saturday nights resolving customers' application operations issues with the OpSource team, he decided to join the vendor community and bring better solutions to prevent operations issues in the first place.
Sign up for Computerworld eNewsletters.