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

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 policies (r…

How Does ITIL Help in the Management of the SDLC?

I was recently asked how ITIL helps in the management of the SDLC (Software Development Lifecycle).  Simply put... SDLC is a Lifecycle approach to produce the software or the "product".  ITIL is a Lifecycle approach that focuses on the "service".
I’ll start by reviewing both SDLC and ITIL Lifecycles and then summarize:
SDLC  -  The intent of an SDLC process is to help produce a product that is cost-efficient, effective and of high quality. Once an application is created, the SDLC maps the proper deployment of the software into the live environment. The SDLC methodology usually contains the following stages: Analysis (requirements and design), construction, testing, release and maintenance.  The focus here is on the Software.  Most organizations will use an Agile or Waterfall approach to implement the software through the Software Development Lifecycle.
ITIL  -  is a best practice for IT service management (ITSM) that focuses on aligning IT services with the needs …

Incidents when a Defect is Involved

Question: We currently track defects in a separate system than our ticket management system. With that said, my question is does anyone have suggestions and/or best practices on how to handle incidents when a defect is involved? Should the incident be closed since the defect is being worked on in another defect tracking system if it is noted in the incident ticket? I am considering creating an incident statuses of 'closed-unresolved' so the incident can still be reported on in our ticket management system but know it is being worked on/tracked in the defect system. With defects, it is possible that we may never work on them because they are very low priority and the impact is low to the user. However, in some cases a defect is being worked on. Should we create a problem ticket instead?
Thanks, René W.

Answer: RenĂ©. In ITIL, the activity you are describing is handled by the Problem Management process. ITIL does not use the term “defect” but it does use the term “known error” to…