<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments for Slow Leadership	</title>
	<atom:link href="https://slowleadership.de/comments/feed/" rel="self" type="application/rss+xml" />
	<link>https://slowleadership.de/</link>
	<description></description>
	<lastBuildDate>Mon, 30 Jan 2023 16:45:12 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.1.1</generator>
	<item>
		<title>
		Comment on Backlog Prioritization Techniques by Cheet Sheat: Sprint Planning - Slow Leadership		</title>
		<link>https://slowleadership.de/blog-post/backlog-prioritization-techniques/#comment-9</link>

		<dc:creator><![CDATA[Cheet Sheat: Sprint Planning - Slow Leadership]]></dc:creator>
		<pubDate>Mon, 30 Jan 2023 16:45:12 +0000</pubDate>
		<guid isPermaLink="false">https://slowleadership.de/?p=270#comment-9</guid>

					<description><![CDATA[[&#8230;] Review the items in the product backlog and prioritize them based on business value, risk, and dependencies. [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] Review the items in the product backlog and prioritize them based on business value, risk, and dependencies. [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Scrum Roles: Scrum Master, Product Owner, Development Team by Using Scrum in Marketing: An Extensive Guide - Slow Leadership		</title>
		<link>https://slowleadership.de/blog-post/scrum-roles-scrum-master-product-owner-development-team/#comment-8</link>

		<dc:creator><![CDATA[Using Scrum in Marketing: An Extensive Guide - Slow Leadership]]></dc:creator>
		<pubDate>Mon, 30 Jan 2023 14:24:57 +0000</pubDate>
		<guid isPermaLink="false">http://slowleadership.de/?p=149#comment-8</guid>

					<description><![CDATA[[&#8230;] Scrum, there are three main roles: the Product Owner, the Scrum Master, and the Development Team. In a marketing context, the Product Owner could be the marketing manager or a product manager, the [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] Scrum, there are three main roles: the Product Owner, the Scrum Master, and the Development Team. In a marketing context, the Product Owner could be the marketing manager or a product manager, the [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on What is Scrum and Why Use It? by Scrum vs Kanban: A Practical Guide to Choosing the Right Approach - Slow Leadership		</title>
		<link>https://slowleadership.de/blog-post/what-is-scrum/#comment-7</link>

		<dc:creator><![CDATA[Scrum vs Kanban: A Practical Guide to Choosing the Right Approach - Slow Leadership]]></dc:creator>
		<pubDate>Mon, 30 Jan 2023 12:49:48 +0000</pubDate>
		<guid isPermaLink="false">https://demosites.io/blogger-gb/?p=38#comment-7</guid>

					<description><![CDATA[[&#8230;] Scrum and Kanban are two of the most widely used Agile methodologies for managing and completing projects. While both frameworks share the Agile principles of flexibility and collaboration, they have distinct differences in approach, processes, and ideal use cases. In this article, we will explore the differences between Scrum and Kanban, and provide a practical guide for choosing the right approach for your project. [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] Scrum and Kanban are two of the most widely used Agile methodologies for managing and completing projects. While both frameworks share the Agile principles of flexibility and collaboration, they have distinct differences in approach, processes, and ideal use cases. In this article, we will explore the differences between Scrum and Kanban, and provide a practical guide for choosing the right approach for your project. [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Facilitating and Leading Scrum Teams by How Scaled Scrum can be adapted to manage hardware development - Slow Leadership		</title>
		<link>https://slowleadership.de/scrum-achieving-agile-excellence-in-the-modern-workplace/the-role-of-the-scrum-master/facilitating-and-leading-scrum-teams/#comment-6</link>

		<dc:creator><![CDATA[How Scaled Scrum can be adapted to manage hardware development - Slow Leadership]]></dc:creator>
		<pubDate>Wed, 25 Jan 2023 00:33:45 +0000</pubDate>
		<guid isPermaLink="false">http://slowleadership.de/?p=231#comment-6</guid>

					<description><![CDATA[[&#8230;] when adapting Scaled Scrum to manage hardware development is the need for strong Scrum Masters to facilitate communication, ensure that everyone is on the same page, and remove any roadblocks that may be preventing [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] when adapting Scaled Scrum to manage hardware development is the need for strong Scrum Masters to facilitate communication, ensure that everyone is on the same page, and remove any roadblocks that may be preventing [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Scrum Events: Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective by 4 best practices for hardware development in Scaled Scrum - Slow Leadership		</title>
		<link>https://slowleadership.de/blog-post/scrum-ceremonies-sprint-planning-daily-scrum-sprint-review-sprint-retrospective/#comment-5</link>

		<dc:creator><![CDATA[4 best practices for hardware development in Scaled Scrum - Slow Leadership]]></dc:creator>
		<pubDate>Wed, 25 Jan 2023 00:24:16 +0000</pubDate>
		<guid isPermaLink="false">http://slowleadership.de/?p=153#comment-5</guid>

					<description><![CDATA[[&#8230;] Scaled Scrum encourages regular communication and collaboration between teams, through regular ceremonies such as daily stand-ups, sprint review and planning meetings, allowing teams to stay aligned and [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] Scaled Scrum encourages regular communication and collaboration between teams, through regular ceremonies such as daily stand-ups, sprint review and planning meetings, allowing teams to stay aligned and [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Backlog Prioritization Techniques by 4 best practices for hardware development in Scaled Scrum - Slow Leadership		</title>
		<link>https://slowleadership.de/blog-post/backlog-prioritization-techniques/#comment-4</link>

		<dc:creator><![CDATA[4 best practices for hardware development in Scaled Scrum - Slow Leadership]]></dc:creator>
		<pubDate>Wed, 25 Jan 2023 00:11:17 +0000</pubDate>
		<guid isPermaLink="false">https://slowleadership.de/?p=270#comment-4</guid>

					<description><![CDATA[[&#8230;] early on. Additionally, it is important to have a clear product backlog, with well-defined and prioritized user stories, to ensure that the project stays aligned with customer needs and the teams work towards the same [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] early on. Additionally, it is important to have a clear product backlog, with well-defined and prioritized user stories, to ensure that the project stays aligned with customer needs and the teams work towards the same [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on Scrum Artifacts: Product Backlog, Sprint Backlog, Increment by What is Scrum and Why Use It? - Slow Leadership		</title>
		<link>https://slowleadership.de/scrum-achieving-agile-excellence-in-the-modern-workplace/scrum-framework/scrum-artifacts-product-backlog-sprint-backlog-increment/#comment-3</link>

		<dc:creator><![CDATA[What is Scrum and Why Use It? - Slow Leadership]]></dc:creator>
		<pubDate>Sun, 22 Jan 2023 14:22:43 +0000</pubDate>
		<guid isPermaLink="false">http://slowleadership.de/?p=155#comment-3</guid>

					<description><![CDATA[[&#8230;] key feature of Scrum is its use of &#8220;Product Backlogs&#8221; and &#8220;Sprint Backlogs.&#8221; The Product Backlog is a prioritized list of all the work that needs to be done on a project or [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] key feature of Scrum is its use of &#8220;Product Backlogs&#8221; and &#8220;Sprint Backlogs.&#8221; The Product Backlog is a prioritized list of all the work that needs to be done on a project or [&#8230;]</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		Comment on How Scaled Scrum can be adapted to manage hardware development by The Agile Mindset and Scrum Principles - Slow Leadership		</title>
		<link>https://slowleadership.de/blog-post/how-scaled-scrum-can-be-adapted-to-manage-hardware-development/#comment-2</link>

		<dc:creator><![CDATA[The Agile Mindset and Scrum Principles - Slow Leadership]]></dc:creator>
		<pubDate>Sun, 22 Jan 2023 14:21:44 +0000</pubDate>
		<guid isPermaLink="false">https://slowleadership.de/?p=285#comment-2</guid>

					<description><![CDATA[[&#8230;] Manifesto was originally developed for software development, its principles can also be applied to hardware development. The Agile approach emphasizes flexibility and adaptability, which can be particularly beneficial [&#8230;]]]></description>
			<content:encoded><![CDATA[<p>[&#8230;] Manifesto was originally developed for software development, its principles can also be applied to hardware development. The Agile approach emphasizes flexibility and adaptability, which can be particularly beneficial [&#8230;]</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
