<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Right good data or The right good data?</title>
	<atom:link href="http://dpadvantage.wordpress.com/2011/05/05/right-good-data-or-the-right-good-data/feed/" rel="self" type="application/rss+xml" />
	<link>http://dpadvantage.wordpress.com/2011/05/05/right-good-data-or-the-right-good-data/</link>
	<description></description>
	<lastBuildDate>Wed, 22 May 2013 15:00:31 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Suzy</title>
		<link>http://dpadvantage.wordpress.com/2011/05/05/right-good-data-or-the-right-good-data/#comment-356</link>
		<dc:creator><![CDATA[Suzy]]></dc:creator>
		<pubDate>Fri, 02 Mar 2012 11:29:06 +0000</pubDate>
		<guid isPermaLink="false">https://dpadvantage.wordpress.com/2011/05/05/right-good-data-or-the-right-good-data/#comment-356</guid>
		<description><![CDATA[Great post. We need to know weather we have the right data or we can also have a &lt;a href=&quot;http://www.qas.co.uk&quot; rel=&quot;nofollow&quot;&gt;data quality&lt;/a&gt; analysis for our business. Thought I&#039;d share!]]></description>
		<content:encoded><![CDATA[<p>Great post. We need to know weather we have the right data or we can also have a <a href="http://www.qas.co.uk" rel="nofollow">data quality</a> analysis for our business. Thought I&#8217;d share!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: George Mallory and Data Mountaineering &#124; The Data Roundtable</title>
		<link>http://dpadvantage.wordpress.com/2011/05/05/right-good-data-or-the-right-good-data/#comment-321</link>
		<dc:creator><![CDATA[George Mallory and Data Mountaineering &#124; The Data Roundtable]]></dc:creator>
		<pubDate>Wed, 11 May 2011 14:02:25 +0000</pubDate>
		<guid isPermaLink="false">https://dpadvantage.wordpress.com/2011/05/05/right-good-data-or-the-right-good-data/#comment-321</guid>
		<description><![CDATA[[...] Managing data for the sake of managing data doesn’t accomplish the business objectives of your organization.  Data management is not about climbing every data mountain just “because it’s there.”  Read the Julian Schwarzenbach blog post about making sure you are improving the right data: Right good data or The right good data? [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Managing data for the sake of managing data doesn’t accomplish the business objectives of your organization.  Data management is not about climbing every data mountain just “because it’s there.”  Read the Julian Schwarzenbach blog post about making sure you are improving the right data: Right good data or The right good data? [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Julian Schwarzenbach</title>
		<link>http://dpadvantage.wordpress.com/2011/05/05/right-good-data-or-the-right-good-data/#comment-319</link>
		<dc:creator><![CDATA[Julian Schwarzenbach]]></dc:creator>
		<pubDate>Fri, 06 May 2011 08:29:13 +0000</pubDate>
		<guid isPermaLink="false">https://dpadvantage.wordpress.com/2011/05/05/right-good-data-or-the-right-good-data/#comment-319</guid>
		<description><![CDATA[John,

Thanks for the excellent comments, as you say it is essential for an organisation wide (or at least directorate wide) functional review to ensure that you are only managing required data. 

Sometimes I have seen practitioners busy &#039;polishing&#039; existing data and claiming great success/progress etc. as this is easier to achieve than taking the wider view. 

Senior managers and executives should ensure that their teams have analysed the current business data requirements before engaging in other data improvement activities.

Julian]]></description>
		<content:encoded><![CDATA[<p>John,</p>
<p>Thanks for the excellent comments, as you say it is essential for an organisation wide (or at least directorate wide) functional review to ensure that you are only managing required data. </p>
<p>Sometimes I have seen practitioners busy &#8216;polishing&#8217; existing data and claiming great success/progress etc. as this is easier to achieve than taking the wider view. </p>
<p>Senior managers and executives should ensure that their teams have analysed the current business data requirements before engaging in other data improvement activities.</p>
<p>Julian</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Owens Dunedin</title>
		<link>http://dpadvantage.wordpress.com/2011/05/05/right-good-data-or-the-right-good-data/#comment-318</link>
		<dc:creator><![CDATA[John Owens Dunedin]]></dc:creator>
		<pubDate>Fri, 06 May 2011 06:05:58 +0000</pubDate>
		<guid isPermaLink="false">https://dpadvantage.wordpress.com/2011/05/05/right-good-data-or-the-right-good-data/#comment-318</guid>
		<description><![CDATA[Excellent points.

The simple rule that makes it easy to ascertain what data is required is, &quot;The only data that an enterprise should hold is that required to support the Business Functions of the enterprise - nothing more, nothing&quot;.  

It is critical to differentiate here between Business Functions and Processes.  The former are the core activities of the enterprise, the latter the sequence in which these activities need to be performed in order to arrive at a particular business outcome.

Functions (not Processes) create, use and transform all enterprise data.  By doing a CRUD matrix (&lt;b&gt;C&lt;/b&gt;reate, &lt;b&gt;R&lt;/b&gt;ead, &lt;b&gt;U&lt;/b&gt;pdate, &lt;b&gt;D&lt;/b&gt;elete) for each Business Function, an enterprise will know exactly what data is required to be held and can archive everything else.

When &quot;polishing up&quot; their data, enterprises ought also be aware of &lt;a href=&quot;http://integrated-modeling-method.com/dataquality/pitfalls-data-re-use/&quot; title=&quot;The Pitfalls of Data Re-Use&quot; rel=&quot;nofollow&quot;&gt;The Pitfalls of Data Re-Use&lt;/a&gt;

Regards
John]]></description>
		<content:encoded><![CDATA[<p>Excellent points.</p>
<p>The simple rule that makes it easy to ascertain what data is required is, &#8220;The only data that an enterprise should hold is that required to support the Business Functions of the enterprise &#8211; nothing more, nothing&#8221;.  </p>
<p>It is critical to differentiate here between Business Functions and Processes.  The former are the core activities of the enterprise, the latter the sequence in which these activities need to be performed in order to arrive at a particular business outcome.</p>
<p>Functions (not Processes) create, use and transform all enterprise data.  By doing a CRUD matrix (<b>C</b>reate, <b>R</b>ead, <b>U</b>pdate, <b>D</b>elete) for each Business Function, an enterprise will know exactly what data is required to be held and can archive everything else.</p>
<p>When &#8220;polishing up&#8221; their data, enterprises ought also be aware of <a href="http://integrated-modeling-method.com/dataquality/pitfalls-data-re-use/" title="The Pitfalls of Data Re-Use" rel="nofollow">The Pitfalls of Data Re-Use</a></p>
<p>Regards<br />
John</p>
]]></content:encoded>
	</item>
</channel>
</rss>
