<?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>Project Management Guide &#187; Configuration Management</title>
	<atom:link href="http://www.pmvista.com/category/configuration-management/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pmvista.com</link>
	<description>- a comprehensive guide for all Software Project Managers and aspiring PMs</description>
	<lastBuildDate>Thu, 03 Dec 2009 16:09:26 +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>Configuration Audit Checklist</title>
		<link>http://www.pmvista.com/configuration-audit-checklist/</link>
		<comments>http://www.pmvista.com/configuration-audit-checklist/#comments</comments>
		<pubDate>Tue, 02 Jun 2009 16:31:49 +0000</pubDate>
		<dc:creator>P</dc:creator>
				<category><![CDATA[Configuration Management]]></category>
		<category><![CDATA[FCA]]></category>
		<category><![CDATA[PCA]]></category>

		<guid isPermaLink="false">http://www.pmvista.com/?p=74</guid>
		<description><![CDATA[Below is a sample configuration audit checklist (for FCA and PCA). The Project Managers can use the following checklist as a reference for the readiness of the audit or even for doing the audit. Release audit: Does the release documentation clearly define the scope of release, including the CRs that should be incorporated? Are all [...]]]></description>
			<content:encoded><![CDATA[<p><!-- ckey="27BFD597" --><br />
Below is a sample configuration audit checklist (for FCA and PCA). The Project Managers can use the following checklist as a reference for the readiness of the audit or even for doing the audit.</p>
<p><span id="more-74"></span></p>
<p><strong>Release audit:</strong></p>
<ul>
<li>Does the release documentation clearly define the scope of release, including the CRs that should be incorporated?</li>
<li>Are all dependencies / bugs been documented?</li>
<li>Is there adequate documentation that identifies the environment to recreate the release?</li>
<li>Is there adequate documentation that specifies the components and the versions of those components that comprise the release?</li>
<li>Are all the items of the release in sync with each other?</li>
<li>Has the release been created using the right versions of the right components from the right repositories?</li>
</ul>
<div id="in_post_ad_middle_1" style="margin: 5px;padding: 0px;">Sponsored Links:
<script type="text/javascript"><!--
google_ad_client = "pub-0090152418549394";
/* 468x60, created 5/12/09 */
google_ad_slot = "4355755295";
google_ad_width = 468;
google_ad_height = 60;
//-->
</script>
<script type="text/javascript"
src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script></div><p><strong>Repository/Configuration item audit:</strong></p>
<ul>
<li>Are the repositories defined as per the SCM plan?</li>
<li>Have the items been put into the correct repositories?</li>
<li>Are the required items present in the repositories?</li>
<li>Have the items been named according to the conventions specified in the SCM plan?</li>
<li>Are the version numbers of items according to the SCM plan?</li>
<li>Have all items been put in the repositories according to the events defined in the SCM plan?</li>
<li>Do the items have required documentation to identify the item, version and the change history?</li>
</ul>
<p><strong>Change Implementation Audit:</strong></p>
<ul>
<li>Have all the required CRs been closed?</li>
<li>Do CRs identify all items to be changed?</li>
<li>Have all items identified for change in the CR been changed?</li>
<li>Is it possible to isolate the changes between any two versions of the items?</li>
<li>Is the documentation in the items adequate to trace the changes back to the appropriate CR?</li>
<li>Is there adequate means to go back to a previous means?</li>
<li>Are there any changes between two versions of an item that are not traceable to an approved CR?</li>
<li>Are the CRs documented before making changes in items?</li>
<li>Are CRs analysed, evaluated and approved prior to making of the change in items?</li>
</ul>
<p><strong>Other aspects to Audit:</strong></p>
<ul>
<li>Are appropriate back ups of repositories been taken?</li>
<li>Has the recovery from back up been tested?</li>
<li>Are there any unauthorized components available in the working directories of the team members?</li>
<li>Is there adequate security/authorization to ensure that only authorized team members perform the check-in and check-out?</li>
</ul>
<p class="facebook"><a href="http://www.facebook.com/share.php?u=http://www.pmvista.com/configuration-audit-checklist/" target="_blank"><img src="http://www.pmvista.com/wp-content/plugins/add-to-facebook-plugin/facebook_share_icon.gif" alt="Share on Facebook" title="Share on Facebook" /></a><a href="http://www.facebook.com/share.php?u=http://www.pmvista.com/configuration-audit-checklist/" target="_blank" title="Share on Facebook">Share on Facebook</a></p><div style='clear:both'></div>]]></content:encoded>
			<wfw:commentRss>http://www.pmvista.com/configuration-audit-checklist/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
