<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Leading requirements</title>
	<atom:link href="http://www.contenthere.net/2008/11/leading-requirements.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.contenthere.net/2008/11/leading-requirements.html</link>
	<description>Enter Content Here</description>
	<lastBuildDate>Fri, 12 Mar 2010 02:28:17 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Adriaan Bloem</title>
		<link>http://www.contenthere.net/2008/11/leading-requirements.html/comment-page-1#comment-927</link>
		<dc:creator>Adriaan Bloem</dc:creator>
		<pubDate>Tue, 10 Feb 2009 09:23:05 +0000</pubDate>
		<guid isPermaLink="false">http://www1.contenthere.net/2008/11/leading-requirements.html#comment-927</guid>
		<description>So true, but something that needs to be said... over and over again. 

Of course, a major problem is that a CMS can take a fair chunk of budget. So it has to be selected &quot;objectively&quot;, which is why project teams come up with these hundreds of requirements. At least, no one will be able to say they selected the CMS on a whim ;)

The second thing is that most teams go through selecting a CMS maybe once every three or four years. They have very little experience with it -- it may only be the second or third time they try (or the first time). That&#039;s why they should get someone in to help who has experience, it&#039;ll save resources and help prevent failure. 

Get someone like Seth. /free plug ;)</description>
		<content:encoded><![CDATA[<p>So true, but something that needs to be said&#8230; over and over again. </p>
<p>Of course, a major problem is that a CMS can take a fair chunk of budget. So it has to be selected &#8220;objectively&#8221;, which is why project teams come up with these hundreds of requirements. At least, no one will be able to say they selected the CMS on a whim <img src='http://www.contenthere.net/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
<p>The second thing is that most teams go through selecting a CMS maybe once every three or four years. They have very little experience with it &#8212; it may only be the second or third time they try (or the first time). That&#8217;s why they should get someone in to help who has experience, it&#8217;ll save resources and help prevent failure. </p>
<p>Get someone like Seth. /free plug <img src='http://www.contenthere.net/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Siggy</title>
		<link>http://www.contenthere.net/2008/11/leading-requirements.html/comment-page-1#comment-753</link>
		<dc:creator>Siggy</dc:creator>
		<pubDate>Sat, 22 Nov 2008 10:18:00 +0000</pubDate>
		<guid isPermaLink="false">http://www1.contenthere.net/2008/11/leading-requirements.html#comment-753</guid>
		<description>I have to say as a CMS vendor (SilverStripe) the pain is felt on our end to. Come to us with 1000 requirements  and seemingly little context as to how to answer those requirements as they support your business/government/NGO needs, and the RFP is either painful, not worth responding to, or just a gamble.</description>
		<content:encoded><![CDATA[<p>I have to say as a CMS vendor (SilverStripe) the pain is felt on our end to. Come to us with 1000 requirements  and seemingly little context as to how to answer those requirements as they support your business/government/NGO needs, and the RFP is either painful, not worth responding to, or just a gamble.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Hobbs</title>
		<link>http://www.contenthere.net/2008/11/leading-requirements.html/comment-page-1#comment-750</link>
		<dc:creator>David Hobbs</dc:creator>
		<pubDate>Wed, 19 Nov 2008 17:06:00 +0000</pubDate>
		<guid isPermaLink="false">http://www1.contenthere.net/2008/11/leading-requirements.html#comment-750</guid>
		<description>Thanks for the useful post.  I would agree that leading requirements are the holy grail.  If only a) isolating them and b) using them as a direct input to narrow the field was easier.  I still wonder if there isn&#039;t something like &quot;Ten Questions&quot; that someone looking for a CMS could answer, and immediately hone in on just a handful of potential CMSes.  I certainly don&#039;t have the questions or answers, but wonder if these leading questions could be generated once in order to get straight to the leading requirements.</description>
		<content:encoded><![CDATA[<p>Thanks for the useful post.  I would agree that leading requirements are the holy grail.  If only a) isolating them and b) using them as a direct input to narrow the field was easier.  I still wonder if there isn&#8217;t something like &#8220;Ten Questions&#8221; that someone looking for a CMS could answer, and immediately hone in on just a handful of potential CMSes.  I certainly don&#8217;t have the questions or answers, but wonder if these leading questions could be generated once in order to get straight to the leading requirements.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
