Skip to main content

DevOps Leader

Image
By
"Culture eats strategy for breakfast." Peter Drucker

“Every company wants to behave like a software company.” Sanjay Mirchandani

As the business environment continues to evolve and change, an adoption of a digital-first mindset is taking place in boardrooms across the globe. Today’s organizations face a never-ending torrent of change from the dynamics of global economics and competition, to the ever more rapid advancements in technology. These can be perceived as both an opportunity and a threat. The ability to adapt and innovate rapidly in this environment has become a core organizational competency. A leader is needed to bring about this change.

Adoption of DevOps can bring about those needed changes that allow an organization to remain competitive in today’s market space. A successful DevOps transformation begins with a value stream map which can allow us to see a time diagnostic of our delivery lifecycle. This flow-based representation gives us an end to end view of how the work is currently being done. From this, we can then begin to identify bottlenecks, waste and ultimately improvement opportunities which will lead to the changes in systems development, processes, introduction of new technologies, reduced time to market, less waste, improved quality, and innovative products and services. 

Organizations that have successfully adopted DevOps are able to deliver a better customer experience with significantly greater operational efficiency and agility. There is a fundamental change happening in the way we develop, deliver, support and maintain our IT services. Organizations that don’t embrace these ways of working will likely be left behind. At the core of this change is changing the way people think (mindset). It isn’t until we begin to change this mindset, that we can then begin to change the culture of our organization. Strategies and bold ideas don’t go far unless the people who must implement them understand and believe in what they are doing. Change must be led.

We must begin to create a generative culture through implementation of tangible DevOps practices. High cooperation through the use of cross-functional teams encourages bridging across silo walls by breaking down those walls paving the way for greater cooperation, communication and the acceptance of a shared vision. Ideas are implemented when experimentation is allowed. Failure leads to inquiry because mistakes are viewed as a learning tool through blameless post-mortems. 

Changing culture is hard! It will take longer and cost more then you plan for. Changing the organization can be accomplished through three phases: 
  • Phase 1: Preparing for the change – Lead the change, create a shared vision, shape the vision (your organizations ‘why’) 
  • Phase 2: Manage the change – Mobilize the change, create pilot programs, communicate successes 
  • Phase 3: Reinforce change – Rollout gains from pilots, monitor progress, solidify gains 
“The ultimate goal of a DevOps transformation is arriving at the self- organizing system in which teams collaborate effectively simply because that’s how things are done, simply because they trust, understand and respect each other.” Anton Weiss

For more information https://www.itsmacademy.com/dol
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 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

The New Four Ps of Service Management

By
By Donna Knapp For years, people , process , and technology (PPT) was a widely recognized framework for balancing and integrating the components needed to achieve optimal performance and outcomes. In the ITIL v3 Service Design publication, this framework was expanded to the four Ps: people , processes , products , and partners . ITIL 4 has further expanded and evolved this framework to the four dimensions of service management. These four dimensions are collectively critical to the effective and efficient facilitation of value for customers and other stakeholders in the form of products and services. The four dimensions of service management are: Organizations and people Information and technology Partners and suppliers Value streams and processes. These four dimensions represent perspectives which are relevant to the whole service value system (SVS), including the entirety of the service value chain and all ITIL practices. Each ITIL practice is a set of organizational resources base...
Post a Comment
Read more