IT Operating Environments Best Practices - Training and Education (TRN / EDU) - preparing administrators and users for deployment
IT Operating Environments Best Practices
Training and Education (TRN / EDU) - preparing administrators and users for deployment
Overview
The Training and Education environment is where administrators and end users are prepared to operate a solution that is approaching or has already reached Production deployment. TRN/EDU serves a purpose that is distinct from all other environments in the pipeline: it is not a testing environment, and the activities performed in it are not validation activities. It is a learning environment, designed to allow trainees to interact with the solution in conditions that are sufficiently realistic to prepare them for Production use without creating risk to Production data, Production state, or other users’ Production experience. A solution deployed to Production without adequate user training consistently produces higher support burden, lower adoption rates, and more user-generated errors than one for which users are properly prepared before they begin using the Production system.
Best Practice
Govern the TRN/EDU environment as a purpose-built learning space that is configured to approximate the Production user experience closely enough for effective training while being fully isolated from Production data and Production state. The TRN/EDU environment should use training-specific data that is realistic in structure and representative in scenario coverage but contains no real PII, PCI, PHI, PFI, or other sensitive information. Training activities in TRN/EDU should not affect Production data, Production records, or other users’ Production state in any way.
The TRN/EDU environment may be used before the solution reaches Production - to train users in advance of deployment - or after Production deployment - to onboard new users or train on new features without using the Production system for learning activities. Both uses are appropriate and should be supported by the environment’s configuration and governance. Establish a defined lifecycle for TRN/EDU environments: they should be provisioned when training programs require them, maintained to a current and accurate configuration while in active use, and decommissioned when the training program is concluded and no active use is planned in the near term.
Benefit(s)
A well-governed TRN/EDU environment reduces the Production risk and support burden that result from deploying solutions to users who have not been adequately prepared to use them. Users who have practiced in TRN/EDU before Production go-live are more confident, make fewer errors, and require less post-deployment support than users who encounter the solution for the first time in Production. The Training environment also protects Production data and Production state from the errors that are inevitable in a learning context - users who accidentally delete records, create incorrect transactions, or misconfigure settings while learning do so in TRN/EDU, where the consequences are inconsequential, rather than in Production, where they may require significant recovery effort.
Copyright for the International Foundation for Information Technology (IF4IT): 2008 - Present
Legal Disclaimers