Do you know test environment management management challenges? June 29, 2018 – Posted in: Service Management – Tags: ,

Test environment management (TEM) is about directing, controlling and managing a test environment. It is a relatively immature discipline. More than 50% of organisations consider test environment management as a major challenge. 20-30% of development and test cycle loss in productivity is due to IT environments. However, as organisations now look to accelerate application delivery and adopt more agile approaches to development, there is a need to improve the way that non-production environments are managed.

Inefficient use of test environments, along with increased demand for environmental resources, can lead to contention and delays on the path to production. As business IT landscapes are becoming more complex and integrated, it’s increasingly becoming more challenging to manage test environments. Some of the key test environment challenges are as follows:

  • The absence of a centralised environment management function — in most of the organisation there is no dedicated team to manage the test environment, most of the time environments are managed by temporary staff which can cause spikes in release cost and also increase the rate of defect leak into production.
  • The absence of a environment management tool — in most of the organisation a spreadsheet is the only tool to manage the test environment. This impacts on environment consolidation and it is hard to track underutilised or overutilised environment, and to manage conflicts. This also results in a large volume of decentralised information, infrastructure and license over-proliferation, etc.
  • Lack of visibility on demand and utilisation.
  • Defects due to the inaccurate configuration in environments.
  • Lack of visibility on test environment availability and configuration.
  • Project teams work in silos and there is a absence of a enterprise view of releases. Releases are project level and not grouped together. Each business unit owns its projects.
  • Best practices are not defined and implemented, with none or little documentation and reusable value.

If you want to know more, please read Test Environment Management.

« Project Management for All!
How you influence human behaviour in services »