Skip to main content

The EVOLUTION of the ENGINEER – Site Reliability Engineers

ALL CALL SREs REQUIRED! 

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.
and…
  • 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.



Comments

Popular posts from this blog

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, which is people. Because the people element adds variability, the service is variable. This holds true, especially for the value proposition—not eve...

What Is A Service Offering?

The ITIL 4 Best Practice Guidance defines a “Service Offering” as a description of one or more services designed to address the needs of a target customer or group.   As a service provider, we can’t stop there!   We must know what the contracts of our service offering are and be able to put them into context as required by the customer.     Let’s explore the three elements that comprise a Service Offering. A “Service Offering” may include:     Goods, Access to Resources, and Service Actions 1. Goods – When we think of “Goods” within a service offering these are the items where ownership is transferred to the consumer and the consumer takes responsibility for the future use of these goods.   Example of goods that are being provided in the offering – If this is a hotel service then toiletries or chocolates are yours to take with you.   You the consumer own these and they are yours to take with you.      ...

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

This article was originally published in 2015. With the Introduction of ITIL 4, some of this best practice has changed. See  ITIL 4 and the Evolving Role of Roles . Updated Definitions in ITIL 4: Process Owner: In ITIL 4, the concept of 'processes' has expanded into broader 'practices.' Consequently, the Process Owner is now often referred to as the 'Practice Owner.' This individual is accountable for the overall design, performance, integration, and improvement of a specific practice within the organization. They ensure that the practice achieves its intended outcomes and aligns with the organization's objectives. Process Manager: Now commonly known as the 'Practice Manager' in ITIL 4, this role is responsible for the day-to-day management of the practice. The Practice Manager ensures that activities are carried out as intended, manages resources assigned to the practice, and oversees the practitioners performing the work. Process Practit...