<?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>Free Project Management Software &#187; criteria for agile tools</title>
	<atom:link href="http://freeprojectmanagementsoftware.org/tag/criteria-for-agile-tools/feed/" rel="self" type="application/rss+xml" />
	<link>http://freeprojectmanagementsoftware.org</link>
	<description></description>
	<lastBuildDate>Fri, 18 May 2012 17:35:52 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Criteria for Commercial Agile Tools?, Part Four</title>
		<link>http://freeprojectmanagementsoftware.org/criteria-for-commercial-agile-tools-part-four/</link>
		<comments>http://freeprojectmanagementsoftware.org/criteria-for-commercial-agile-tools-part-four/#comments</comments>
		<pubDate>Fri, 01 May 2009 20:33:34 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Agile Tooling]]></category>
		<category><![CDATA[agile tools]]></category>
		<category><![CDATA[criteria for agile tools]]></category>

		<guid isPermaLink="false">http://freeprojectmanagementsoftware.org/?p=79</guid>
		<description><![CDATA[This week Free Project Management Software is dedicating its space to a discussion of what organizations should look for when evaluating agile tooling solutions. Today’s post examines the RFP’s sections on Enterprise Scalability, Data and Security, and Support. Enterprise Scalability Is your tool an industry standard? How many users use your tool? Can users be [...]]]></description>
			<content:encoded><![CDATA[<p><em>This week Free Project Management Software is dedicating its space to a discussion of what organizations should look for when evaluating <a href="http://agilemethodology.org/" target="_blank">agile</a> tooling solutions. Today’s post examines the RFP’s sections on Enterprise Scalability, Data and Security, and Support. </em></p>
<p><span style="text-decoration: underline;">Enterprise Scalability</span></p>
<ul>
<li> Is your tool an industry standard?  How many users use your tool?</li>
<li> Can users be managed via enterprise directory authentication such as Active Directory and LDAP?</li>
<li> Are integrations with common bug-tracking applications available?</li>
<li> Does the tool have the ability to support distributed teams?</li>
<li> Has your tool been deployed for 500+ users on a single instance at a single customer site?  1,000+ users?</li>
<li> Can you provide three large-customer references? Please list three multi-hundred user installations, approximate number of users, and primary contact.</li>
</ul>
<p><span style="text-decoration: underline;">Data and Security</span></p>
<ul>
<li> Do you support automated and manual backups?</li>
<li> Are client-server communications encrypted with SSL?</li>
<li> Do you support encrypted enterprise directory authentication such as LDAPS?</li>
<li> Do you offer a technology escrow option in case adversity befalls your organization?</li>
<li> How is programmatic access to the data provided in your tool?</li>
<li> Does the tool have a web services API for data access and integration purposes?  Please describe the scope of the API.</li>
<li> If your tool is remotely hosted, please provide a detailed outage history.</li>
<li> If your tool is remotely hosted, please provide uptime SLA.</li>
<li> If your tool is remotely hosted, how often do you have scheduled maintenance downtimes?</li>
</ul>
<p><span style="text-decoration: underline;">Support</span></p>
<ul>
<li> Describe your technical support options.</li>
<li> How many times per year do you release?</li>
<li> Can customers choose when to upgrade?</li>
<li> Does the tool offer an in-depth, online product manual?</li>
<li> Is documentation built into the tool?</li>
<li> Can technical support be accessed directly through the tool?</li>
<li> What percentage of features released were originally requested by users?</li>
<li> What is the process for requesting features?</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://freeprojectmanagementsoftware.org/criteria-for-commercial-agile-tools-part-four/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

