Skip to main content

DevOps for Newbies

You may have heard a lot of buzz around the DevOps movement that is taking hold in today’s industry where service management quality and efficiency are paramount.   The term "DevOps" was popularized through a series of "DevOps Days" starting in 2009 in Belgium and it is said by those present that they knew they were witnessing something very different and unique.  They knew they were on the verge of something that would change the way that all service providers designed, developed and delivered services in every industry.  Since then, there have been DevOps Days conferences held in India, Brazil, Australia, Germany, and Sweden and other parts of the globe including the United States. 

So what is it?
Business demand is increasing! That is not news. The need to produce services fast is increasing!  We know that methods such as Agile, Scrum and others that have increased capability for development of products but we must recognize that as only one element in the value stream where quality and speed are required.   Between the business and the consumer are many functions and roles that are required to deliver and sustain the operational support for the life of the service.  Between the business and the consumer all the way from Development through to Operations (Dev/Ops) industries demand a fluid, fast and efficient cohesiveness in the value stream.  Not only because we must deliver, but because it is a critical success factor for those organizations that wish be able to compete and stay in business.  DevOps is much more than just the development team cooperating with the operational team and vice versa. 

DevOps is a cultural and professional movement that at its core breaks down silos for the delivery and management of new or changed services that are required to meet the ever increasing business demand in almost every industry in the world.  The “us vs. them” mentality that plays out in many areas of service delivery between the functions of development and operations will not endure.

What will it take?
We must change the culture and although there are tools and automation techniques to assist you in your DevOps initiatives the only way to move a culture is to move the people involved.  Ongoing communication and education for both the IT staff and managers is required including a comprehensive understanding for:
  • Benefits to the business
  • Concepts and practices (including its relationship to Agile, Lean and IT Service Management (ITSM)
  • Improved workflows – In the entire value stream!
  • Improved communication and feedback loops
  • Reliance on automation
  • Application of DevOps in an enterprise environment
  • Critical success factors and key performance indicators (how to measure for success!) 
Today the DevOps movement has evolved and those early adopters are now reaping the benefits as high performing service providers.  For more information including training and certification for DevOps:  http://www.itsmacademy.com/Detail.bok?no=148 

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