Friday , March 24 2017
ITMPI FLAT 003
Main Menu
Home / Project Management / Risk Management / 5 Deadly Mistakes in IT Operations to Avoid

5 Deadly Mistakes in IT Operations to Avoid

The life of IT operations is stressful. They need to introduce more business functionality and minimize digital spending, all while trying not to make mistakes that hinder the ability to respond to business needs. Bernd Harzog, in an article for Network World, lists five IT operations mistakes that can have disastrous results on the company:

  1. Letting security rule the roost
  2. Organizing by IT silo
  3. Organizing by IT layer
  4. Firing all of your smart domain experts
  5. Having a cloud-first strategy

Use Your Expertise in the Right Place

Security is the biggest concern these days, but taking a security-first approach too far can become an impassable barrier as opposed to a necessary evil. To maximize protection against threats and minimize disruption to agility will take time. Some risk will always factor into your strategy, but the impacts of risks can be reduced if you have proper strategies.

Many IT organizations have different teams who are domain experts in their own area. But if each has their own tools without the ability to share information across silos, quality of service will ultimately be capped far below what is really possible. Avoiding a silo mentality may also require reorganization with cloud computing services such as IaaS, PaaS and SaaS. But imagine this situation:

So, the IaaS team owns all of the hardware… The PaaS team owns all of the infrastructure software above the hypervisor and below the applications themselves… And the SaaS teams own the applications in the JVMs and everything in the containers.

The trap [in this situation]is that boundaries of these layers are defined by abstraction layers such as the hypervisor, the JVM and the container. Each abstraction layer makes it very hard to see how things above the layer interact with things below the layer… The key here is to pursue approaches to metric collection and monitoring that span these layers of abstraction so that you have a full top-to-bottom view of… the stack (otherwise known as an end-to-end view).

You don’t need a specific type of cloud strategy, such as a public cloud-first strategy, in all situations. A bias towards any particular kind of execution environment does not put the needs of the business as a priority. A proper cloud strategy should start with the requirements of the business that owns the application first. And an important last thing to remember is that, when you outsource, make sure to do so intelligently. Marry outsourcer skills with in-house skills for the best results.

You can view the original article here: http://www.networkworld.com/article/3157443/cloud-computing/5-deadly-mistakes-in-agile-it-operations.html

About My Nguyen

Profile photo of My Nguyen
My is a staff writer for AITS. She has a varied background in writing and marketing, having previously worked for the World & Vietnam Report among others.

Check Also

Managing Distributed Projects

Projects are increasingly distributed across different sites. But distributed teams and suppliers complicate communication and ...

Leave a Reply

Your email address will not be published. Required fields are marked *

Get the best IT management articles right in your inbox
Subscribe
Join 15K subscribers