Configuration Gap
An unsatisfied environment demand is called a Configuration Gap.
Examples of configuration gaps:
  • you have to test version 2.0 on an environment but current version deployed is 1.1
  • you cannot find an environment with the configuration required to reproduce a bug detected in production
  • you booked an environment to train end users but it is extremely slow and unstable (performance test running at the same time)
Impacts of configuration gaps vary a lot from situation and the type of environments involved. Configuration gaps in production are often considered as Incidents.
Last modified 1yr ago
Copy link