LF

How Smelly
Are Your IT Environments?

31

MARCH, 2017

Kent beck, the inventor of XP extreme programming, once wrote about the concept of “Smelly Code”.

Given IT Environments seem to be a significant challenge for so many organizations, it got us thinking:

What might “Smelly IT Environments” smell of?

 

In a nutshell, here is our top 8 list of things that indicate your IT & Test Environments smell like a Kipper.

  1. Use of spreadsheets to manage & track your Test Environments
  2. A CMDB that only ever focuses on the Infrastructure Components
  3. Too many Test Environment System Instances (causing overspend)
  4. Too few Test Environment System Instances (causing contention)
  5. Inability to identify current and future Test environment demand
  6. Lack of End to End Data Integrity
  7. Inconsistent & Slow IT Environment operations
  8. Manual information gathering & reporting

Learn more about implementing IT Environment Transparency & Governance with enov8.

 

How smelly are your IT Environments?

Relevant Articles

The DevOps Void & Value Stream Mapping

Do you ever wonder why the environment preparation or releases take so long? After all, the company just invested “zillions” on a whole bunch of great tools and a cloud framework.

Benchmarking Release Management

It goes without saying, that the backbone of all organizations today is digital and independent of the end-products you provide, there is an inherent need to drive your features and solutions from conception to production…

Sand Castles and DevOps at Scale

DevOps & DevOps at Scale is little a bit like comparing the building of Sand Castles on a Beach to Town Planning. Here are 5 practices to promote as a way of preparing for a DevOps at scale capability…