DZone

Implementing SRE is fundamentally about shifting culture, but it often means adding new tooling and processes to your team’s workflows to support that cultural change. Teams add new steps and checks to incident response procedures. Incident responders write retrospectives and create new meetings to review them. Engineers consult new tools like monitoring dashboards and SLOs. In other words, SRE creates another layer of consideration in development and operations.

With all of these additions, it may seem inevitable that new steps would slow down the process. But investing in reliability will actually save you time. In this blog post, we’ll look at how SRE tightens feedback loops and decreases friction, and how development velocity generates business value.

Source: DZone