Skip to main content

The EVOLUTION of the ENGINEER – Site Reliability Engineers


Let’s take a walk down to the ocean and while you consider the opportunity, benefits, and $$$, think about dipping your toe in. Let’s explore Reliability, Site Reliability, and the Site Reliability Engineer

No doubt the world is evolving. People are evolving and tech is evolving. Business and customer requirements are evolving. The evolution of systems requires the evolution of engineers. Nature and pandemics put undue stress on our resources! In comes the Certified Site Reliability Engineer

"Urgent, Urgent, Urgent… All hands on deck!", is a call that practitioners, managers, and organizations do not want to hear and recognize must stop!

Reliability – At a minimum, we recognize that the delivery of service is not dependent solely on the quality of the product itself and the goal is not that the products or service merely be deployed. A service must be operated and sustained over a period. How long? For the life of the service. Or in some cases, until you close the doors.
But, ask yourself:

  • Once identified, How long does it take for an incident to reach the right team?
  • Could it be minutes instead of hours or even days? Why then is it taking so long?
  • What is the percentage of repeat incidents against all incidents reported?
  • Can repeat incidents be reduced to NEVER AGAIN?
Site Reliability - Requires systems thinking. Systems and ecosystems generate outcomes to deliver value. The outcomes of those systems must be able to withstand storms or some type of failure and remain functional for the consumer/customer usability. Systems thinking and user experience are essential. Site Reliability puts the “ability” in “reliable”.

Site Reliability Engineers – Shift Left
  • Have a special skillset applied to the architecture, design, and development of products and services.
  • Spend 50% of time and skills in Systems Engineering – application design, data structures, key integrations, and development tasks.
  • Spend 50% of their time contributing to the ongoing operation of systems in production and systems engineering problems.
SREs understand and contribute support for improved systems affecting infra, operating systems, networks, and databases both for today and for the future. They ensure availability, observability, efficiency, and reliability holistically.

Site Reliability Engineers embed themselves into cross-functional Agile and DevOps teams and continuously lean into the opportunity to … Educate and Inspire.


Popular posts from this blog

What is the difference between Process Owner, Process Manager and Process Practitioner?

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you. Roles and Responsibilities: Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance. Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables.  An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and th

Four Service Characteristics

Recently I came across several articles by researchers and experts that laid out definitions and characteristics of services. ITIL provides us with a definition that can help drive the creation of value-laden services: A means of delivering value to customers by facilitating outcomes customers want to achieve without the ownership of specific costs and risks. An area that ITIL is not so clear is in terms of service characteristics. Several researchers and experts put forth that services have four basic characteristics (IHIP): ·          Intangibility—Services are the results of actions not things. They have no physical presence and represent a logical set of elements. One way to think of service is “work done for others.” ·          Heterogeneity—Also known as “variability”; services are unique items because of the mechanisms used to deliver services-that is people. Because the people element adds variability, the service is variable. This holds true especially for the v

How Does ITIL Help in the Management of the SDLC?

I was recently asked how ITIL helps in the management of the SDLC (Software Development Lifecycle).  Simply put... SDLC is a Lifecycle approach to produce the software or the "product".  ITIL is a Lifecycle approach that focuses on the "service". I’ll start by reviewing both SDLC and ITIL Lifecycles and then summarize: SDLC  -  The intent of an SDLC process is to help produce a product that is cost-efficient, effective and of high quality. Once an application is created, the SDLC maps the proper deployment of the software into the live environment. The SDLC methodology usually contains the following stages: Analysis (requirements and design), construction, testing, release and maintenance.  The focus here is on the Software.  Most organizations will use an Agile or Waterfall approach to implement the software through the Software Development Lifecycle. ITIL  -  is a best practice for IT service management (ITSM) that focuses on aligning IT services with the