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,
Given IT Environments seem to be a significant challenge for so many organizations,
- Causing over 20% lost Testing Productivity (World Quality Report)
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 Test Environments smell like a Kipper.
- Use of excel spreadsheets to manage & track your Test Environments
- A CMDB that only ever focuses on the Hardware Components
- Too many Test Environment System Instances or Components (causing overspend)
- Too few Test Environment System Instances or Components (causing contention)
- Inability to identify current and future Test environment demand or usage (no test environment bookings)
- Lack of End to End Test Data Integrity (causing testing to fail and grind to a halt)
- Inconsistent & Slow IT Environment operations (heroics and manual intervention)
- Manual information gathering & reporting (typically the use of PowerPoint)
Ref: Edited from Original Source smelly-environments
