Test Environment Management Use Case
by Niall Crawford
Test Environment Management Use Case
We often get asked by people “What is TEM (Test Environment Management), well for those of you looking for a quick overview of Test Environment Management, here is Use Case we developed as way of explanation.
In a nutshell, Test Environment Management “Use Case” it is about ensuring the Environment Managers, Project Managers, Test Mangers, Developers, Engineers & System SMEs (Subject Matter Experts) collaborate to ultimately ensure Environment transparency, readiness and ultimately stability of your environments across the life-cycle.
And this “Use Case” can all be described in 9 simple steps:
Step#1 Know what your IT Environments look like. As we see it, if you can’t understand (and model) your Production or Test environments your chances of managing them effectively are next to negligible.
Step#2 Understand & Capture the demand and usage of your Test Environments. Demand will initially come from the overarching Portfolios & Projects and early insight will ensure you can proactively plan, coordinate and provide fit for purpose environments in a timely fashion.
Step#3 Understand & Capture the demand and usage of your Development & Test teams (via Test Environment Bookings). And align these requirements back to definable SDLC phases and operations like SIT & User Acceptance Testing.
Step#4 Ensure all your Test Environment activity & operations are planned, centralized and communicated. Key people involved might include the system owner, the infrastructure, application and data engineers involve in provisioning and those involved in testing quality and health.
Step#5 Ensure your customers (the purveyors of your environment) are continually supported. Ensure you establish some fundamental service management so incidents can be dealt with quickly and requests for change & release can be adequately controlled.
Step#6 Coordinate your day to day environment events and release operations using effective scheduling and standard operating procedure (run-books).
Step#7 Look to streamline the most common operations (e.g. system shakedown) by replacing manual methods with automated tools & methods.
Step#8 Analyse Environment Activity, Health, Usage & Availability & produce reports to share with the team and your stakeholders.
Step #9 Continually learn & evolve by using the centralized information at your disposal, look for opportunities to reduce your test environment footprints, streamline your release operations, streamline your DevOps activities and establish methods to reduce IT environment disruption.
Ultimately with the intention of:
- Operational Uplift across DevOps & Test
- IT Cost Optimization
- Reduced DevTest Disruption
- Reduced IT Environment Spend &
- Accelerated Delivery (Time to Market)
About enov8: enov8 is a specialist software engineering house that has established the world’s leading IT & Test Environment management platform. A solution that addresses all the requirements in the above use case and much more through a broad range of supporting functions including modules for Environments Management, Visual Configuration Management, Service Management, Enterprise Release Management, Release Management & Resilience.
20 MAY, 2019 by Mark Henke It’s a great step when teams deliberately manage their deployments instead of treating them as second-class citizens to writing code. But there are many pitfalls to managing deployments effectively. Many things lurk, waiting to trip us up....
08 MAY, 2019 by Mark Henke Taking enterprise release management seriously is a great step toward helping our organization flourish. Embracing release management will allow us to make the invisible visible. We’ll be able to effectively manage how work flows through our...
04 MAY, 2019 by Rodney Smith If you work in an organization that uses the scaled agile framework (SAFe), chances are it's not a small company. It's enterprise-y. It's probably gone through some growing pains, which is a good problem to have in the business sense. The...
29 APRIL, 2019 by Carlos "Kami" Maldonado "DevOps at scale" is what we call the process of implementing DevOps culture at big, structured companies. Although the DevOps term was coined almost 10 years ago, even in 2018 most organizations still haven't completely...
24 APRIL, 2019 by Mark Robinson It’s the normal case with software buzzwords that people focus so much on what something is that they forget what it is not. DevOps is no exception. To truly embrace DevOps and cherish what it is, it’s important to comprehend what it...
16 April, 2019 by Eric Goebelbecker Your organization is in the midst of an agile transformation. You know that agile is the way to go, and you're looking forward to, or maybe already reaping, some of the benefits. Who can argue with what agile brings to the table?...