The Test Environment Management Plan Template
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 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)
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.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.
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
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 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.
04 JANUARY, 2021 by Ukpai Ugochi Have you ever wondered what would happen if you mistakenly added bugs to your codes and shipped them to users? For instance, let's say an IT firm has its primary work tree on GitHub, and a team member pushes codes with bugs to the...
07 DECEMBER 2020 by Daniel de Oliveira In today’s application-based world, companies are releasing more applications than ever before. Software delivery life cycles are becoming more complicated. As a result, large companies require hundreds and even thousands of test...
19 NOVEMBER, 2020 by Michiel Mulders What Makes a Good Test Data Manager? Have you implemented test data management at your organization? It will surely benefit you if your organization processes critical or sensitive business data. The importance of test data is...
22 October, 2020 by Louay Hazami Data privacy is one of the most pressing issues in the new digital era. Data holds so much value for normal internet users and for all types of companies that are looking to capitalize on this new resource. To keep data anonymous and...
18 SEPTEMBER 2020 by Arnab Chowdhury Every aspect of our daily lives involves the usage of data. Be it our social media, banking account, or even while using an e-commerce site, we use data everywhere. This data may range from our names and contact information to our...
09 SEPTEMBER, 2020 by Michiel Mulders Do you want your company to scale efficiently? Look for an enterprise release manager (ERM). An ERM protects and manages the movements of releases in multiple environments. This includes build, test, and production environments....