<?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: Always consider the source when doing research</title>
	<atom:link href="http://blog.mastykarz.nl/always-consider-the-source-when-doing-research/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.mastykarz.nl/always-consider-the-source-when-doing-research/</link>
	<description>Innovation Matters &#124; SharePoint Server MVP &#124; ISSN 2210-9390</description>
	<lastBuildDate>Thu, 09 Feb 2012 05:22:29 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: alan pelz-sharpe</title>
		<link>http://blog.mastykarz.nl/always-consider-the-source-when-doing-research/comment-page-1/#comment-3414</link>
		<dc:creator>alan pelz-sharpe</dc:creator>
		<pubDate>Fri, 11 Jul 2008 06:44:43 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mastykarz.nl/2008/07/08/always-consider-the-source-when-doing-research/#comment-3414</guid>
		<description>Hi there,
as one of the authors of the CMS Watch report on SharePoint (The SharePoint Report 2008) and a principal at CMS Watch I felt I had to answer this one ;-)
The fact is there is a lot of positive comment from us regarding MOSS, and any reader of  our extensive research would know that - at every presentation I make on the topic I stress the fact that I think MOSS is an excellent product.
However, it is not perfect - and there are occasions when it is not a good fit for buyers, and buyers are who we write for not vendors.  Vendors are criticized equally by CMS Watch - and we never ever work for vendors. This is a stark contrast to other analyst firms out there.
MOSS is a good product - but unfortunately too many people have bought it to use in unsuitable situations - it has been miss sold by the channel - sometimes accidentally sometimes deliberately.  Microsoft&#039;s own definition of ECM differs from the rest of the industry causing more confusion. And frankly there are some major deployments out there in Fortune 500 firms that have gone terribly wrong.
So we see our job as dishing out the good and the bad - ensuring buyers are well informed and well armed.  The cheerleading we will leave to the vendors - be that Microsoft, EMC, IBM or anyone else.
Hope this helps to clarify ;-)
Best
Alan</description>
		<content:encoded><![CDATA[<p>Hi there,<br />
as one of the authors of the CMS Watch report on SharePoint (The SharePoint Report 2008) and a principal at CMS Watch I felt I had to answer this one ;-)<br />
The fact is there is a lot of positive comment from us regarding MOSS, and any reader of  our extensive research would know that &#8211; at every presentation I make on the topic I stress the fact that I think MOSS is an excellent product.<br />
However, it is not perfect &#8211; and there are occasions when it is not a good fit for buyers, and buyers are who we write for not vendors.  Vendors are criticized equally by CMS Watch &#8211; and we never ever work for vendors. This is a stark contrast to other analyst firms out there.<br />
MOSS is a good product &#8211; but unfortunately too many people have bought it to use in unsuitable situations &#8211; it has been miss sold by the channel &#8211; sometimes accidentally sometimes deliberately.  Microsoft&#039;s own definition of ECM differs from the rest of the industry causing more confusion. And frankly there are some major deployments out there in Fortune 500 firms that have gone terribly wrong.<br />
So we see our job as dishing out the good and the bad &#8211; ensuring buyers are well informed and well armed.  The cheerleading we will leave to the vendors &#8211; be that Microsoft, EMC, IBM or anyone else.<br />
Hope this helps to clarify ;-)<br />
Best<br />
Alan</p>
]]></content:encoded>
	</item>
</channel>
</rss>

