
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.
- Use of spreadsheets to manage & track your Test Environments
- A CMDB that only ever focuses on the Infrastructure Components
- Too many Test Environment System Instances (causing overspend)
- Too few Test Environment System Instances (causing contention)
- Inability to identify current and future Test environment demand
- Lack of End to End Data Integrity
- Inconsistent & Slow IT Environment operations
- Manual information gathering & reporting
Learn more about implementing IT Environment Transparency & Governance with enov8.
