Chapter 66. The Best Advice I Can Give to Teams
Nicole Forsgren
If I had to say one thing, it would be this: integrate your teams.
That’s it. That’s the advice. Work together. Talk more.
If there’s one thing we’ve learned about developing and delivering software over the past decade (or more), it’s that more communication and fewer silos is key. It really is all about information flow. It should come as no surprise that this applies to SRE teams, too. Carving off another special team simply creates a new silo, and their work and influence can’t reach those who need it most. By separating the SRE team from the development teams they support—sometimes by creating a Center of Excellence—you end up causing more problems than you solve. Separating SRE from dev teams leads to a few problems, including:
- Elitism
- I get it; it feels good to be part of the special club, but by isolating expertise, you simply create a bottleneck and limit the ability for others to get work done. This can lead to everyone coming to you for everything in a case of learned helplessness, or coming to you for nothing because the process is too hard. Neither of these is good because they remove you from important, high-priority work.
- Knowledge constraints
- When one central group owns and hoards all the knowledge, it becomes harder to share, mentoring is more difficult, and best practices become more difficult ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access