Skip to main content

Agile / DevOps: (_____) as CODE #DevOps

Image
By
Infrastructure as Code – is a common term among developers, architects, and operational staff and the practice has evolved in response to demand for quality and efficiency in the industry.  Over the last decade many organizations have come to realize that the essence of Infrastructure as Code is to treat the configuration of systems the same way that software source code is treated.  Frequent code integration, automated builds, and integrated testing have resulted in stronger IT performance and therefore business value.

Security as Code – An increase in security breaches across all industries has brought forward a similar concept, and that is to look at “Security as Code”.  This concept would include the usage of repeatable algorithms to integrate security checks with each code check.  This expands the scope of traditional “Continuous Integration” and automation.  Organizations realize that security is no longer a second thought and must be addressed at the front of the value stream.  We must be able to gather security requirements at the same rate and importance as the functional requirements.  Security is integrated throughout the entire development, test and deployment stream. The result is that code is not only in a releasable state (Continuous Delivery) but rather code is now in a “Secure” releasable state.

Availability as Code – If the value of “Infrastructure as Code” and “Security as Code” is understood than it is not a far stretch to realize the true essence of “Availability as Code”.  While availability engineering is mostly about reducing unplanned downtime, “Availability as Code” will help us to also reduce planned downtime.  Availability as Code / Designing for Availability is the only way that some organizations will ever be able to truly move from a reactive to a proactive state.  Biggest gains here include customer confidence and increase in market share.  Relieving the “Ninjaneers” from operational firefighting allows organizations to leverage that skill set in the design/development lifecycle stage where repeatable and automated algorithms, builds and testing evolve with business demand.

Warranty as Code - We know that the application alone won’t get us there.  We now realize that integrating Infrastructure as Code helps but is not all inclusive.  Best Practice for ITSM defines “Warranty” as specified levels of Availability, Capacity, Continuity and Security.  In order to realize value with efficiency industries could benefit from looking at each of these elements as… “CODE”.   Where are you in your DevOps journey?  What are your thoughts? 

For more information please see http://www.itsmacademy.com/agile/
Labels:

Comments

Post a Comment

Popular posts from this blog

Four Service Characteristics

By
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...
Post a Comment
Read more

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

By
This article was originally published in 2015. With the Introduction of ITIL 4, some of the concepts have changed in ways that are described below. ITIL 4 has also introduced new roles, as explained in our blog ITIL 4 and the Evolving Role of Roles . Before we dive into the difference between these roles, let’s first look at a key update in ITIL 4 – the shift from processes to practices. ITIL 4 has evolved to focus on holistic practices vs. isolated processes. By definition, a practice is a set of organizational resources designed for performing work or accomplishing an objective. For example, the purpose of the incident management practice is to minimize the negative impact of incidents by restoring normal service operation as quickly as possible. All organizations recognize the need to allocate resources to the management of incidents and mature their capabilities in that area. In ITIL 4, each practice includes resources based on the four ...
1 comment
Read more

What Is A Service Offering?

By
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.      ...
Post a Comment
Read more