LF

The Test Environment Management Plan Template

13

AUGUST, 2019

by Jane Temov

So, you’ve been asked to write a “Test Environment Management Plan”? Or perhaps you just want to write a plan to baseline your current non-production processes, outline future test environment strategy and/or educate those around you.

* Definition: “Test Environment Management Plan”

A plan, focused on Test Environment Management (or non-production environment management), that will promote a better level of visibility across one’s test environments and operations and establish proactive controls / standards to ensure they are effectively managed, used, shared, serviced and provisioned (and/or deleted) in an efficient manner.

 

Two Questions

Two question we often get asked at Enov8 is where does one begin and/or can you provide a good example.

In response to the first question, where does one begin

we often point them back to two key reference points.

The IEEE’s recommended minimum standard for process for Configuration Management.

An overarching guideline for Test Environment Maturity.

Firstly, because at the heart of Test Environment Management is Configuration Management. There is no getting away from it, the heart of good TEM is Identification, Managements, Status Accounting & Audit. And secondly TEM is more than simply Configuration Management, TEM has associated “nuances” that move into the wider world of Agile, ITSM & ITOM.

In response to the second, can we provide a good example

we often scratch our head 🙁 … You see, the problem with providing an example is there are not many good samples of a Test Environment Plan available online. In fact, it is often hard enough to find “good” Configuration Management Plans, and people have been writing these since the seventies.

So, with that in mind, we decided to put together a template (a simple guideline) that other people can follow and leverage. A template that shares many of the structural elements you might expect to find in a Configuration Management Plan, but with an extra twist aligned to the IT & Test Environment Management Maturity Index.

 

Example TEM Plan Template Structure

Test Environment Management Plan (Light Version)

1 Introduction

Tip: Initial TEM introduction, scoping & context.

1.1 Purpose of the TEM Plan

1.2 Scope of Document

Tip: In addition to TEM process we suggest you describe at a high level,  your Test Environment(s) your supporting here.  

1.3 Definitions, Acronyms and Abbreviations

1.4 Document References

1.5 Document Overview

2 The TEM Team Structure

Tip: High Level overview of TEM team structure & enablers.

2.1 Organisation

2.2 Responsibilities

2.3 Tools & Infrastructure

3 The TEM Process

Tip: Define how each primary process will be realized (think People, Process & Tools)

3.1 Knowledge Management

Refer: Mapping your Environments.

3.2 Demand Management

3.3 Planning & Coordination

3.4 Service Management

3.5 Data Operations

3.6 Application Operations

3.7 Infrastructure Operations

3.8 Status Accounting & Reporting

4 Plan Outcomes

Outline the primary benefits of implementing this Test Environment Management plan.

For example:

The intention / benefits of implementing this plan can be summarized as follow:

  • End to End visibility of Test Environments
  • End to End Visibility of Activity
  • Operational Standardization
  • Increased DevTest productivity
  • Reduced Environment Incidents / Disruption
  • Accelerated IT Project Delivery
  • IT Cost Optimization / Controlled Spend i.e. spend based on need & usage.

5 Implementation Project Plan

Tip” Describe how we will get there.

5.0 Project Resources

5.1 Delivery Milestone Plan

5.2 Actor Training Plan

5.3 Optimization Plan

6 Appendix

 

A Concise Download Version

For a more concise version of above (with section explanations) please download our PDF example.

Post Authoring Review

Happy with your document and/or new processes?

  • Hold regular retrospectives with stakeholders & team members to get ideas for improvement.
  • And use our online EMMI calculator to compare it against the EMMI methodology.

There are always opportunities to optimize.

Want to learn more about how to improve your Test Environment Management?

If you are interested in learning more about implementing a mature IT & Test Environment Management capability in your organisations then speak to enov8 about enov8 Environment Manager. Enov8 Environment Manager is the only complete platform that takes you across the Environment Management, Release & Data Spectrum.

Jane Temov

Jane is an experienced IT Environments Management & Resilience Evangelist. Areas of specialism include IT & Test Environment Management, Disaster Recovery, Release Management, Service Resilience, Configuration Management, DevOps &Infra/Cloud Migration. 

Relevant Articles

How Data Breaches Happen?

08 OCTOBER, 2019 by Michiel Mulders Preamble You’ve probably seen some recent articles asserting that the world’s most valuable resource is no longer oil—it’s data. New internet titans like Google, Amazon, Apple, Facebook, and Microsoft look unstoppable. In fact,...

DevOps and TEM Go Hand in Glove

25 SEPTEMBER, 2019 by Mark Henke DevOps is overall a healthy practice for most development teams, but it doesn’t come for free. Enterprises are eager to adopt the practice but their tools often lag behind DevOps practices. This is a bit like walking out into the...

Data Security (Scale and Bees)

25 AUGUST, 2019 by Jane Temov Data security, The problem is scale & a lack of bees One of the biggest challenges of securing one’s enterprise data is the sheer volume. Think about it. Hundred (perhaps Thousands) of Applications, Thousands (perhaps Tens of Thousands)...

Five Reasons You Need Enterprise Configuration Management

02 AUGUST, 2019 by Eric Olsson Preamble Software is buggy. It's a bold claim, I know. Sarcasm aside, the battle to keep your applications up and running is ongoing. Wouldn't it be nice if you had a way to eliminate an entire class of bugs from your application?...

Software Testing Anti Patterns

15 JULY, 2019 by Peter Morlion Martin Fowler AntiPattern "An antipattern is a solution that initially looks like an attractive road lined with flowers... but further on leads you into a maze filled with monsters."   Since the dawn of computers, we’ve always had to...

A Brief History of Configuration Management

26 June, 2019 by Justin Reynolds Gone are the days of monolithic software applications. In today’s microservices-and-continuous-integration driven world, where apps run in hybrid cloud environments and users engage with them on any device and on any underlying...