IT Operating Environments Best Practices

Overview

SLA commitments that are either too high or too low for the purpose and user population of an environment create problems at both extremes. SLA commitments that are too high for a lower environment - requiring Production-equivalent uptime from a DEV environment - impose infrastructure and operational costs that are disproportionate to the value of the environment and that consume resources that could be better invested in higher-tier environments where availability has greater organizational impact. SLA commitments that are too low for an environment that is heavily used and delivery-critical - best-effort availability for a shared SIT environment used by twenty teams in active sprint delivery - create a governance standard that accepts delivery disruption as normal rather than treating it as an accountability failure.

Best Practice

Calibrate SLA commitments for each environment to the realistic needs of the teams and activities it serves, the organizational impact of its unavailability, and the infrastructure investment required to meet the defined commitment. Before setting an environment SLA, assess: how many teams or individuals depend on the environment and for what activities; what is the organizational productivity cost of environment unavailability measured in terms of team-hours blocked per hour of downtime; and what infrastructure investment is required to achieve the candidate availability level. Use this assessment to set SLA commitments that are demanding enough to protect organizational productivity and flexible enough to be achievable within the infrastructure investment appropriate to the environment tier. Review and adjust SLA commitments whenever significant changes to the environment’s user population, usage patterns, or organizational importance occur.

Benefit(s)

Right-sized SLA commitments produce environment reliability standards that are both achievable and organizationally meaningful. Achievable standards motivate investment in the specific reliability improvements needed to meet them consistently. Meaningful standards create genuine governance accountability for the environments that delivery teams depend on most. The organization directs environment reliability investment to the environments where the productivity and delivery impact of unavailability is highest, rather than distributing investment uniformly across environment tiers regardless of where unavailability creates the greatest organizational cost.