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

The Four Ps of Service Design - It’s not all about Technology

People ask me why I think that many designs and projects often fail. The most common answer is from a lack of preparation and management. Many IT organizations just think about the technology (product) implementation and fail to understand the risks of not planning for the effective and efficient use of the four Ps: People, Process, Products (services, technology and tools) and Partners (suppliers, manufacturers and vendors). A holistic approach should be adopted for all Service Design aspects and areas to ensure consistency and integration within all activities and processes across the entire IT environment, providing end to end business-related functionality and quality. (SD 2.4.2) People:   Have to have proper skills and possess the necessary competencies in order to get involved in the provision of IT services. The right skills, the right knowledge, the right level of experience must be kept current and aligned to the business needs. Products:   These are the technology managem

What Is A Service Offering?

The ITIL4 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 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 than toiletries or chocolates are yours to take with you.   You the consumer own these and they are yours to take with you.               Note: Goods may not always be provided for every Service

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