<?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>Application Lifecycle Management Archives - IntelliTect</title>
	<atom:link href="https://intellitect.com/blog/tag/application-lifecycle-management/feed/" rel="self" type="application/rss+xml" />
	<link></link>
	<description>Complex Software Development - Simplified</description>
	<lastBuildDate>Thu, 23 Feb 2023 18:19:38 +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>Application Lifecycle Management Archives - IntelliTect</title>
	<link></link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>DevOps Metrics</title>
		<link>https://intellitect.com/blog/devops-metrics/</link>
					<comments>https://intellitect.com/blog/devops-metrics/#comments</comments>
		
		<dc:creator><![CDATA[Mark Michaelis]]></dc:creator>
		<pubDate>Tue, 20 Oct 2015 16:36:24 +0000</pubDate>
				<category><![CDATA[DevOps]]></category>
		<category><![CDATA[Application Lifecycle Management]]></category>
		<guid isPermaLink="false">http://intellitect.com/?p=21031</guid>

					<description><![CDATA[<p>Metrics Related to DevOps For the past several months, I have been participating with the DevOps Metrics team following the DevOps Forum 2015 earlier this year. The topic of discussion was Metrics related to DevOps and today I presented on the topic at the 2015 DevOps Enterprise Summit in San Francisco in a talk entitled&#8230;&#160;</p>
<div class="read-more-wrapper"><a href="https://intellitect.com/blog/devops-metrics/" class="button button-primary" rel="bookmark">Read More &#187;<span class="screen-reader-text">DevOps Metrics</span></a></div>
<p>The post <a href="https://intellitect.com/blog/devops-metrics/">DevOps Metrics</a> appeared first on <a href="https://intellitect.com">IntelliTect</a>.</p>
]]></description>
		
					<wfw:commentRss>https://intellitect.com/blog/devops-metrics/feed/</wfw:commentRss>
			<slash:comments>3</slash:comments>
		
		
			</item>
		<item>
		<title>Relative Paths for Visual Studio Generic Tests</title>
		<link>https://intellitect.com/blog/relative-paths-for-visual-studio-generic-tests/</link>
		
		<dc:creator><![CDATA[Mark Michaelis]]></dc:creator>
		<pubDate>Mon, 21 Oct 2013 02:26:38 +0000</pubDate>
				<category><![CDATA[DevOps]]></category>
		<category><![CDATA[Application Lifecycle Management]]></category>
		<category><![CDATA[Testing]]></category>
		<category><![CDATA[Visual Studio]]></category>
		<guid isPermaLink="false">http://intellitect.com/?p=3915</guid>

					<description><![CDATA[<p>Creating a Generic Test To make generic tests robust enough to run for all developers on your team and on the build server, you are likely going to want to avoid hard coding the path to the executable. &#160;To do this successfully, you need to have a list of all the environment variables that are&#8230;&#160;</p>
<div class="read-more-wrapper"><a href="https://intellitect.com/blog/relative-paths-for-visual-studio-generic-tests/" class="button button-primary" rel="bookmark">Read More &#187;<span class="screen-reader-text">Relative Paths for Visual Studio Generic Tests</span></a></div>
<p>The post <a href="https://intellitect.com/blog/relative-paths-for-visual-studio-generic-tests/">Relative Paths for Visual Studio Generic Tests</a> appeared first on <a href="https://intellitect.com">IntelliTect</a>.</p>
]]></description>
		
		
		
			</item>
		<item>
		<title>Work Item to Changeset</title>
		<link>https://intellitect.com/blog/associating-a-work-item-to-a-changeset-after-checking-in/</link>
					<comments>https://intellitect.com/blog/associating-a-work-item-to-a-changeset-after-checking-in/#comments</comments>
		
		<dc:creator><![CDATA[Mark Michaelis]]></dc:creator>
		<pubDate>Fri, 08 Dec 2006 00:56:31 +0000</pubDate>
				<category><![CDATA[Development]]></category>
		<category><![CDATA[Application Lifecycle Management]]></category>
		<guid isPermaLink="false">http://mark.michaelis.net/Blog/AssociatingAWorkItemToAChangesetAfterCheckingIn.aspx</guid>

					<description><![CDATA[<p>Associating a Work Item to a Changeset After Checking In Today I received an email asking how to associate a work item with a change set after all the code was checked in (without performing the association.) It turns out the solution is relatively simple.&#160; On the Links tab of the work item select Add.&#160;&#8230;&#160;</p>
<div class="read-more-wrapper"><a href="https://intellitect.com/blog/associating-a-work-item-to-a-changeset-after-checking-in/" class="button button-primary" rel="bookmark">Read More &#187;<span class="screen-reader-text">Work Item to Changeset</span></a></div>
<p>The post <a href="https://intellitect.com/blog/associating-a-work-item-to-a-changeset-after-checking-in/">Work Item to Changeset</a> appeared first on <a href="https://intellitect.com">IntelliTect</a>.</p>
]]></description>
		
					<wfw:commentRss>https://intellitect.com/blog/associating-a-work-item-to-a-changeset-after-checking-in/feed/</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
			</item>
	</channel>
</rss>
