<?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>Build and Release Management &#187; SCM Agile Development</title>
	<atom:link href="http://allscm.com/archives/category/scm-agile-development/feed" rel="self" type="application/rss+xml" />
	<link>http://allscm.com</link>
	<description>SCM Unleashed!</description>
	<lastBuildDate>Tue, 29 Jun 2010 20:13:31 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Agile Software Configuration Management For Everyone?</title>
		<link>http://allscm.com/archives/agile-software-configuration-management-for-everyone.html</link>
		<comments>http://allscm.com/archives/agile-software-configuration-management-for-everyone.html#comments</comments>
		<pubDate>Tue, 30 Oct 2007 09:17:19 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[SCM Agile Development]]></category>

		<guid isPermaLink="false">http://allscm.com/?p=52</guid>
		<description><![CDATA[Just as the title states, not everyone can adapt to the demanding and unpredictable nature of a build and release engineer&#8217;s job.  We just recently hired an intern for our group to help out with the hectic build implementation tasks.  The intern in question had a website design background which I believed was thoroughly shocked [...]


Related posts:<ol><li><a href='http://allscm.com/consulting-services' rel='bookmark' title='Permanent Link: Consulting Services'>Consulting Services</a> <small>Establish An Accurate and Continuous Build and Release Infrastructure For...</small></li>
</ol>]]></description>
		<wfw:commentRss>http://allscm.com/archives/agile-software-configuration-management-for-everyone.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Daily Stand Up Meetings</title>
		<link>http://allscm.com/archives/daily-stand-up-meetings.html</link>
		<comments>http://allscm.com/archives/daily-stand-up-meetings.html#comments</comments>
		<pubDate>Sun, 30 Sep 2007 08:39:56 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[SCM Agile Development]]></category>

		<guid isPermaLink="false">http://allscm.com/?p=30</guid>
		<description><![CDATA[Another Agile concept we&#8217;ve adopted within our group is the daily stand-up meetings.   At first glance, this may seem like an evil way of micro-managing but that thought quickly dissolves once the values of such meetings started to add up. These daily stand-ups should be conducted just as the title implies; everyone must be [...]


Related posts:<ol><li><a href='http://allscm.com/consulting-services' rel='bookmark' title='Permanent Link: Consulting Services'>Consulting Services</a> <small>Establish An Accurate and Continuous Build and Release Infrastructure For...</small></li>
</ol>]]></description>
		<wfw:commentRss>http://allscm.com/archives/daily-stand-up-meetings.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Build and Release &#8211; Agile Development</title>
		<link>http://allscm.com/archives/build-and-release-agile-development.html</link>
		<comments>http://allscm.com/archives/build-and-release-agile-development.html#comments</comments>
		<pubDate>Thu, 30 Aug 2007 08:32:46 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[SCM Agile Development]]></category>

		<guid isPermaLink="false">http://allscm.com/?p=27</guid>
		<description><![CDATA[Tools such as XPlanner should be the cornerstone of a software configuration management group.  This iteration and user-stories based model planning tool allows software configuration management engineers to have a more complete picture of what the current tasks/projects are and what&#8217;s in the back-burner. The way my current team uses this tool is we break [...]


No related posts.]]></description>
		<wfw:commentRss>http://allscm.com/archives/build-and-release-agile-development.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Configuration Management Policy</title>
		<link>http://allscm.com/archives/configuration-management-policy.html</link>
		<comments>http://allscm.com/archives/configuration-management-policy.html#comments</comments>
		<pubDate>Thu, 19 Jul 2007 08:14:36 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Automated Test Framework]]></category>
		<category><![CDATA[Build Framework]]></category>
		<category><![CDATA[Continuous Integration]]></category>
		<category><![CDATA[Release Framework]]></category>
		<category><![CDATA[SCM Agile Development]]></category>

		<guid isPermaLink="false">http://allscm.com/?p=23</guid>
		<description><![CDATA[To promote the spirit of Agile Development and Continuous Integration, groups of builds must be classified and treated differently within the development organization. These builds are as follows: Engineering: These builds lives on the individual developer&#8217;s machine. It should never see the light of day beyond this scope. This is merely a convenient build tool [...]


No related posts.]]></description>
		<wfw:commentRss>http://allscm.com/archives/configuration-management-policy.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
