<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Agile Archives - IntelliTect</title>
	<atom:link href="https://intellitect.com/blog/tag/agile/feed/" rel="self" type="application/rss+xml" />
	<link></link>
	<description>Complex Software Development - Simplified</description>
	<lastBuildDate>Mon, 07 Aug 2023 20:51:50 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>

<image>
	<url>https://intellitect.com/wp-content/uploads/2017/02/cropped-favicon-1-32x32.png</url>
	<title>Agile Archives - IntelliTect</title>
	<link></link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Agile Demystified: 7 Metrics to Assess Your Agile Practices</title>
		<link>https://intellitect.com/blog/demystified-agile/</link>
		
		<dc:creator><![CDATA[Grant Erickson]]></dc:creator>
		<pubDate>Tue, 21 May 2019 00:53:28 +0000</pubDate>
				<category><![CDATA[Leadership]]></category>
		<category><![CDATA[Agile]]></category>
		<category><![CDATA[demystified]]></category>
		<category><![CDATA[Scrum]]></category>
		<guid isPermaLink="false">https://intellitect.com/?p=35223</guid>

					<description><![CDATA[<p>Evolution of Agile Development Agile development has evolved to become the norm for software projects. Many organizations are practicing agile with fantastic results. However, sometimes results are less than stellar. Assess your company&#8217;s agile practices with this quick checklist. Score 1 point for every answer you agree with. 1. Number of unit tests: Increasing Your&#8230;&#160;</p>
<div class="read-more-wrapper"><a href="https://intellitect.com/blog/demystified-agile/" class="button button-primary" rel="bookmark">Read More &#187;<span class="screen-reader-text">Agile Demystified: 7 Metrics to Assess Your Agile Practices</span></a></div>
<p>The post <a href="https://intellitect.com/blog/demystified-agile/">Agile Demystified: 7 Metrics to Assess Your Agile Practices</a> appeared first on <a href="https://intellitect.com">IntelliTect</a>.</p>
]]></description>
		
		
		
			</item>
		<item>
		<title>Scrum Master Check-In: The Sprint Retrospective</title>
		<link>https://intellitect.com/blog/scrum-master-check-in/</link>
		
		<dc:creator><![CDATA[Casey]]></dc:creator>
		<pubDate>Tue, 21 May 2019 00:50:48 +0000</pubDate>
				<category><![CDATA[DevOps]]></category>
		<category><![CDATA[Agile]]></category>
		<category><![CDATA[Scrum]]></category>
		<guid isPermaLink="false">https://intellitect.com/?p=35197</guid>

					<description><![CDATA[<p>Simple Tricks to Improve the Sprint Retrospective New to Scrum? No problem. Scrum is an agile methodology that allows developers to create working software early and often. Scrum Masters are servant leaders; we seek to guide one or many agile development teams through the Scrum process by facilitating Scrum ceremonies, removing team impediments, and orchestrating&#8230;&#160;</p>
<div class="read-more-wrapper"><a href="https://intellitect.com/blog/scrum-master-check-in/" class="button button-primary" rel="bookmark">Read More &#187;<span class="screen-reader-text">Scrum Master Check-In: The Sprint Retrospective</span></a></div>
<p>The post <a href="https://intellitect.com/blog/scrum-master-check-in/">Scrum Master Check-In: The Sprint Retrospective</a> appeared first on <a href="https://intellitect.com">IntelliTect</a>.</p>
]]></description>
		
		
		
			</item>
		<item>
		<title>Starting the DevOps Journey</title>
		<link>https://intellitect.com/blog/start-devops-journey/</link>
		
		<dc:creator><![CDATA[Phil Spokas]]></dc:creator>
		<pubDate>Thu, 19 Jul 2018 16:40:46 +0000</pubDate>
				<category><![CDATA[Leadership]]></category>
		<category><![CDATA[Agile]]></category>
		<guid isPermaLink="false">https://intellitect.com/?p=33632</guid>

					<description><![CDATA[<p>Is Your Team Ready for DevOps? DevOps, or Development and Operations, is the integration of the people, process and tools required to deliver high-quality software in an agile manner from concept all the way to production. In its simplest terms, these practices holds a development team and operations team together so that they understand what&#8230;&#160;</p>
<div class="read-more-wrapper"><a href="https://intellitect.com/blog/start-devops-journey/" class="button button-primary" rel="bookmark">Read More &#187;<span class="screen-reader-text">Starting the DevOps Journey</span></a></div>
<p>The post <a href="https://intellitect.com/blog/start-devops-journey/">Starting the DevOps Journey</a> appeared first on <a href="https://intellitect.com">IntelliTect</a>.</p>
]]></description>
		
		
		
			</item>
		<item>
		<title>Part 2: Scrum From a QA Perspective</title>
		<link>https://intellitect.com/blog/scrum-from-a-qa-perspective-part-2/</link>
		
		<dc:creator><![CDATA[Mike]]></dc:creator>
		<pubDate>Thu, 17 Dec 2015 00:52:11 +0000</pubDate>
				<category><![CDATA[DevOps]]></category>
		<category><![CDATA[Agile]]></category>
		<category><![CDATA[Scrum]]></category>
		<category><![CDATA[Testing]]></category>
		<guid isPermaLink="false">http://intellitect.com/?p=22271</guid>

					<description><![CDATA[<p>Analyzing Scrum Part 2: There is an excellent blog that describes software development as engineering a bridge: Imagine joining an engineering team. You&#8217;re excited and full of ideas, probably just out of school and a world of clean, beautiful designs, awe-inspiring in their aesthetic unity of purpose, economy, and strength. You start by meeting Mary,&#8230;&#160;</p>
<div class="read-more-wrapper"><a href="https://intellitect.com/blog/scrum-from-a-qa-perspective-part-2/" class="button button-primary" rel="bookmark">Read More &#187;<span class="screen-reader-text">Part 2: Scrum From a QA Perspective</span></a></div>
<p>The post <a href="https://intellitect.com/blog/scrum-from-a-qa-perspective-part-2/">Part 2: Scrum From a QA Perspective</a> appeared first on <a href="https://intellitect.com">IntelliTect</a>.</p>
]]></description>
		
		
		
			</item>
		<item>
		<title>Should Your SCRUM Team Assign Story Points to a Spike?</title>
		<link>https://intellitect.com/blog/should-your-scrum-team-assign-story-points-to-a-spike/</link>
					<comments>https://intellitect.com/blog/should-your-scrum-team-assign-story-points-to-a-spike/#comments</comments>
		
		<dc:creator><![CDATA[IntelliTect]]></dc:creator>
		<pubDate>Mon, 17 Aug 2015 17:17:32 +0000</pubDate>
				<category><![CDATA[DevOps]]></category>
		<category><![CDATA[Agile]]></category>
		<category><![CDATA[Scrum]]></category>
		<guid isPermaLink="false">http://intellitect.com/?p=19171</guid>

					<description><![CDATA[<p>The Great Debate Our team has been discussing the pros and cons of assigning points to a Spike and determining our approach. In case you are unfamiliar with the term Spike (in regards to agile development), the definition, according to agiledictionary.com, is: A story or task aimed at answering a question or gathering information, rather&#8230;&#160;</p>
<div class="read-more-wrapper"><a href="https://intellitect.com/blog/should-your-scrum-team-assign-story-points-to-a-spike/" class="button button-primary" rel="bookmark">Read More &#187;<span class="screen-reader-text">Should Your SCRUM Team Assign Story Points to a Spike?</span></a></div>
<p>The post <a href="https://intellitect.com/blog/should-your-scrum-team-assign-story-points-to-a-spike/">Should Your SCRUM Team Assign Story Points to a Spike?</a> appeared first on <a href="https://intellitect.com">IntelliTect</a>.</p>
]]></description>
		
					<wfw:commentRss>https://intellitect.com/blog/should-your-scrum-team-assign-story-points-to-a-spike/feed/</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
			</item>
		<item>
		<title>Part 1: Scrum From a QA Perspective</title>
		<link>https://intellitect.com/blog/scrum-from-a-qa-perspective/</link>
		
		<dc:creator><![CDATA[Mike]]></dc:creator>
		<pubDate>Thu, 06 Aug 2015 17:49:22 +0000</pubDate>
				<category><![CDATA[DevOps]]></category>
		<category><![CDATA[Agile]]></category>
		<category><![CDATA[Scrum]]></category>
		<category><![CDATA[Testing]]></category>
		<guid isPermaLink="false">http://intellitect.com/?p=18861</guid>

					<description><![CDATA[<p>Fulfilling the Role of a QA Engineer I work QA but am not solely on a QA team; I am a member of a Scrum team. Like the other members, this means I am a part of the development team, I just happen to specialize in QA practices. This is the first position at which&#8230;&#160;</p>
<div class="read-more-wrapper"><a href="https://intellitect.com/blog/scrum-from-a-qa-perspective/" class="button button-primary" rel="bookmark">Read More &#187;<span class="screen-reader-text">Part 1: Scrum From a QA Perspective</span></a></div>
<p>The post <a href="https://intellitect.com/blog/scrum-from-a-qa-perspective/">Part 1: Scrum From a QA Perspective</a> appeared first on <a href="https://intellitect.com">IntelliTect</a>.</p>
]]></description>
		
		
		
			</item>
	</channel>
</rss>
