Inspire, develop, and guide a winning organization.
Create visible workflows to achieve well-architected software.
Understand and use meaningful data to measure success.
Integrate and automate quality, security, and compliance into daily work.
Understand the unique values and behaviors of a successful organization.
LLMs and Generative AI in the enterprise.
An on-demand learning experience from the people who brought you The Phoenix Project, Team Topologies, Accelerate, and more.
Learn how making work visible, value stream management, and flow metrics can affect change in your organization.
Clarify team interactions for fast flow using simple sense-making approaches and tools.
Multiple award-winning CTO, researcher, and bestselling author Gene Kim hosts enterprise technology and business leaders.
In the first part of this two-part episode of The Idealcast, Gene Kim speaks with Dr. Ron Westrum, Emeritus Professor of Sociology at Eastern Michigan University.
In the first episode of Season 2 of The Idealcast, Gene Kim speaks with Admiral John Richardson, who served as Chief of Naval Operations for four years.
New half-day virtual events with live watch parties worldwide!
DevOps best practices, case studies, organizational change, ways of working, and the latest thinking affecting business and technology leadership.
Is slowify a real word?
Could right fit help talent discover more meaning and satisfaction at work and help companies find lost productivity?
The values and philosophies that frame the processes, procedures, and practices of DevOps.
This post presents the four key metrics to measure software delivery performance.
This paper describes how Google’s Site Reliability Engineering (SRE) teams collaborate with their developer (Dev) counterparts to improve the reliability, efficiency, and velocity of Google’s products and infrastructure. The authors explain SRE’s mission and guiding principles, and outline three main types of engagements between SRE and Dev teams.
The paper includes case studies illustrating each engagement type. It also discusses anti-patterns to avoid and how to get engagements back on track when challenges arise. While every organization is different, the core SRE principles around specialist expertise, engineering focus, Dev partnership, and adaptive engagement can be applied flexibly in many contexts.
This paper describes how Google’s Site Reliability Engineering (SRE) teams collaborate with their developer (Dev) counterparts to improve the reliability, efficiency, and velocity of Google’s products and infrastructure. The authors explain SRE’s mission and guiding principles, and outline three main types of engagements between SRE and Dev teams:
1. Baseline engagements: Ad-hoc support and consultation from SRE to help Dev teams with reliability best practices and incident response.
2. Assisted engagements: SRE provides proactive, project-focused support to Dev teams, often related to design and implementation of new products or features. Dev retains primary responsibility for the service.
3. Full support engagements: SRE takes on significant operational responsibilities for critical, evolving services that require the highest reliability. SRE and Dev work in close partnership.
Learn how SRE and Dev teams collaborate effectively to improve reliability and velocity.
Discover the three main types of SRE engagements and when to use each for maximum impact.
Gain insights from real-world case studies of successful and challenging SRE-Dev partnerships.
Understand core SRE principles that can be adapted to optimize your organization's approach.
SRE Engagements Product Area Lead at Google
SRE Manager at Google
Technology exec, SRE, engineering leader, entrepreneur
Engineering Manager (SRE) at Google
Technical writer for Google Site Reliability Engineering in NYC. I previously provided documentation for Google Data Center and Hardware Operations teams. Before moving to New York, I was a lecturer in technical writing at Stanford University.
Run Your Platform like a Business within a...
What Every CIO Needs to Know about GitOps
Learnings for Organizing for Outcomes
Learn More
