DevOps - The Basics

“Change sticks when it becomes the way we do things around here.” ~ John P. Kotter

DevOps benefits the business by improving communication, collaboration and the integration of people, processes and technologies across the IT value stream.

Ultimately, DevOps enables companies to deliver better software faster and more reliably by…

Improving communication, collaboration and the integration of processes and tools across the IT value stream
Automating the process of software delivery and infrastructure changes
Leveraging Agile, Lean, ITSM and evolving DevOps practices

DevOps – The Basics

Get Involved!

DevOps practices will continue to evolve through communities of practice. Seek out opportunities to collaborate with others and to share what you’ve learned.

Change related to DevOps initiatives will affect organizational culture. Effective communication plans, training, and clear policies and procedures are all needed to achieve the desired performance outcomes and enable collaboration between the many stakeholders involved in DevOps. Culture change and progress cannot happen without the support of people like you.

Take action!

Contribute to your organization’s DevOps effort by expanding your knowledge of DevOps principles and practices and by using what you learn to lead improvement activities. Be a change champion!

For more information about DevOps read this great resource from ITSM Academy titled “What is DevOps”

For Certification and Training click here --> inspire & educate…

Comments

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 then 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 Offe

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 the

Search