<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Operations on Ghafoor's Personal Blog</title><link>http://ghafoorsblog.com/categories/operations/</link><description>Recent content in Operations on Ghafoor's Personal Blog</description><generator>Hugo</generator><language>en</language><managingEditor>noreply@example.com (AG Sayyed)</managingEditor><webMaster>noreply@example.com (AG Sayyed)</webMaster><copyright>Copyright © 2024-2026 AG Sayyed. All Rights Reserved.</copyright><lastBuildDate>Fri, 15 May 2026 13:20:20 +0100</lastBuildDate><atom:link href="http://ghafoorsblog.com/categories/operations/index.xml" rel="self" type="application/rss+xml"/><item><title>DevOps Behaviour</title><link>http://ghafoorsblog.com/courses/ibm/devops-content/devops-pcert/01-introduction-to-devops/03-module/003-devops-behaviour/</link><pubDate>Sun, 06 Apr 2025 13:50:47 +0000</pubDate><author>noreply@example.com (AG Sayyed)</author><guid>http://ghafoorsblog.com/courses/ibm/devops-content/devops-pcert/01-introduction-to-devops/03-module/003-devops-behaviour/</guid><description>&lt;p class="lead text-primary"&gt;This document explains the differences between traditional Ops and DevOps, highlighting the cultural clashes, required behavioural changes, and the benefits of adopting DevOps practices.&lt;/p&gt;
&lt;h2 id="traditional-ops-vs-devops"&gt;Traditional Ops vs DevOps&lt;/h2&gt;
&lt;p&gt;Traditional Ops and DevOps represent opposing approaches to managing change and infrastructure. Enterprises often view change as complex, risky, and time-consuming, treating new initiatives as one-time projects with fixed budgets and timelines. DevOps, on the other hand, focuses on breaking large projects into smaller, manageable changes that reduce risk and enable continuous delivery.&lt;/p&gt;</description></item></channel></rss>