Skip to main content

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

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…