Take control of your releases with a free, instant demo.

Launch Now
illustration of a smelly fish to represent smelly it environments

How smelly are your IT environments?

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

How to Clean Up Smelly IT Environments

The good news is that smelly IT environments can be fixed. Most of the odors above share the same root cause: a lack of visibility. When environment information lives in spreadsheets, inboxes and people’s heads, nobody can see the whole picture. Bookings clash, systems sprawl and costs creep up unnoticed.

Start by building a single, up-to-date model of your environments that covers applications, infrastructure, data and the relationships between them. Next, put a simple booking process in place so teams can see current and future demand before contention occurs. Then standardize and automate routine operations such as data refreshes, deployments and health checks, so they run the same way every time.

Finally, measure what matters. Track utilization, availability and outages for each environment, and share those numbers with delivery teams and leadership. An environment that sits idle, or one that is constantly broken, is far easier to spot when the data is in front of you.

Tackle these steps one at a time and the smell soon fades. In its place you get faster delivery, lower spend and far fewer surprises on release day.

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

Smelly IT and Test Environments