<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Scrum-Events on Ghafoor's Personal Blog</title><link>http://ghafoorsblog.com/tags/scrum-events/</link><description>Recent content in Scrum-Events 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, 15 Nov 2025 18:14:57 +0000</lastBuildDate><atom:link href="http://ghafoorsblog.com/tags/scrum-events/index.xml" rel="self" type="application/rss+xml"/><item><title>Scrum Artifacts, Events and Benefits</title><link>http://ghafoorsblog.com/courses/ibm/devops-content/devops-pcert/02-agile-development-and-scrum/01-module/006-artifacts-events/</link><pubDate>Mon, 26 May 2025 16:23:47 +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/006-artifacts-events/</guid><description>&lt;p class="lead text-primary"&gt;
This document explains the key components of Scrum methodology: the three artifacts (Product Backlog, Sprint Backlog, and Done Increment), the five events (Sprint Planning, Daily Scrum, Sprint, Sprint Review, and Sprint Retrospective), and the benefits of implementing Scrum. It also highlights the differences between Scrum and Kanban approaches.
&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="scrum-artifacts"&gt;Scrum Artifacts&lt;/h2&gt;
&lt;p&gt;Scrum defines three primary artifacts that provide transparency and opportunities for inspection and adaptation throughout the development process.&lt;/p&gt;
&lt;h3 id="1-product-backlog"&gt;1. Product Backlog&lt;/h3&gt;
&lt;p&gt;The Product Backlog is a comprehensive list of all requirements and features that have not yet been implemented. It contains all stories planned for future development, representing everything that will eventually be built for the product. Some teams separate their backlog into categories such as &amp;ldquo;icebox&amp;rdquo; or &amp;ldquo;release backlog,&amp;rdquo; but all future work is generally considered part of the Product Backlog.&lt;/p&gt;</description></item></channel></rss>