<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Xp on Ghafoor's Personal Blog</title><link>http://ghafoorsblog.com/tags/xp/</link><description>Recent content in Xp 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>Sat, 16 May 2026 17:45:02 +0100</lastBuildDate><atom:link href="http://ghafoorsblog.com/tags/xp/index.xml" rel="self" type="application/rss+xml"/><item><title>Agile Methodologies</title><link>http://ghafoorsblog.com/courses/ibm/devops-content/devops-pcert/02-agile-development-and-scrum/01-module/002-methodologies/</link><pubDate>Mon, 26 May 2025 09:13:12 +0000</pubDate><author>noreply@example.com (AG Sayyed)</author><guid>http://ghafoorsblog.com/courses/ibm/devops-content/devops-pcert/02-agile-development-and-scrum/01-module/002-methodologies/</guid><description>&lt;p class="lead text-primary"&gt;
This document explores various software development methodologies, contrasting the traditional Waterfall approach with Agile methodologies such as Extreme Programming (XP) and Kanban. It examines the limitations of the sequential Waterfall model and highlights how iterative, feedback-driven approaches address these challenges through continuous improvement, team collaboration, and adaptive planning.
&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="traditional-waterfall-development"&gt;Traditional Waterfall Development&lt;/h2&gt;
&lt;p&gt;The Waterfall approach to software development is a sequential, linear process where each phase must be completed before the next begins. The methodology follows a strict progression through distinct phases:&lt;/p&gt;</description></item></channel></rss>