Skip to main content

You Don't Need a Weatherman to Tell Which Way the Wind is Blowing

Bob Dylan once wrote “The times they are a changing”

DevOps is a cultural and professional movement that improves IT's time to market through better communication, collaboration, integration and automation.  It is the intersection of development (software engineering), technology operations and quality assurance (QA). DevOps is as much about a different way of thinking as it is a different way of behaving.

Dev-Ops is a solution to a business problem - one that requires faster deployments, more innovation and tighter integration with all stakeholders. It is as much of a visionary shift as it is an opportunity to leverage build-deploy-operate technologies.

Visionary shifts require that an organization
  • Create a sense of urgency, to stay stagnant is to fall behind the competition.
  • Form a guiding coalition, get buy in from senior leadership and collaboration with middle management.
  • Create a vision.  Apply agile tenets to the entire service lifecycle, breakdown complex processes into simple modular activities.
  • Communicate the vision. Use every means at your disposal to transform stakeholders through distribution of information and knowledge.
  • Empower others to act. Get people to identify those areas of weakness that cause failure and waste. 
  • Plan for and create short term wins.  Where possible use tools and automation to eliminate.
  • Consolidate improvements and produce more change.  Consolidation will create new skills and enhanced cooperation.
  • Institutionalize the change. Begin to measure your successes and advertise your gains.

Instilling a DevOps culture takes time, leadership and commitment.  Demonstrated results show that it is certainly worth the effort.




     


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