Managed IT Services: Aligning IT Infrastructure Automation To Business Goals If you’re managing an IT infrastructure automation project, are you considering the scope of the project and aspirational business results? This question may seem obvious, but I’ve seen sufficient projects diverted to make it a legitimate one. It’s been my experience that the label of Private Cloud has set an unreliable expectation for both clients and IT. There’s a thought that a private cloud should relate a public cloud in form and features. But IT companies automatically risk scope creep when comparing their project goals to that of public cloud characteristics.
Ten Years For Ten Years Of Experience I once had a manager give me some excellent early-career tips. It went like: it needs ten years to get ten years of experience. The tip may seem simple, but it applies well to IT infrastructure automation efforts. Before even getting to the example of AWS it’s helpful to look at a massive AWS customer, Netflix.
IT Infrastructure Automation Case Study – Netflix As a customer of AWS Cloud, it took Netflix seven years to migrate the majority of its streaming services to AWS. And this is because cloud migration isn’t as simple as taking existing workloads and performing a physical-to-virtual (P2V) migration. Netflix recognized processes and applications need refactoring to run in Cloud infrastructure. The main lesson for companies is that introducing automation-as-a-service to customers isn’t enough. IT infrastructure requires working with the application team to understand how IT infrastructure automation integrates into workflows. One of the basic use cases for IT infrastructure automation is the increase in application development workflows. Managed IT service teams want to ask the fundamental question of what’s the existing workflow and do the automation solution to change that workflow.