<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.3" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Squaring the MDM circle</title>
	<link>http://andyonenterprisesoftware.com/2008/04/squaring-the-mdm-circle/</link>
	<description>Andy Hayler, founder of Kalido and The Information Difference, gives his views on the enterprise software market. Issues covered include data warehousing, master data management, business intelligence and data quality.</description>
	<pubDate>Sat, 11 Oct 2008 00:36:26 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.3</generator>

	<item>
		<title>by: Ad</title>
		<link>http://andyonenterprisesoftware.com/2008/04/squaring-the-mdm-circle/#comment-73506</link>
		<pubDate>Thu, 10 Apr 2008 13:54:44 +0000</pubDate>
		<guid>http://andyonenterprisesoftware.com/2008/04/squaring-the-mdm-circle/#comment-73506</guid>
					<description>This is a real ‘chicken and egg’ problem in any somewhat larger organization. Business governance is often shared across and within several functional and/or geographical business units. Each of these units has its own needs, agenda en funds. IT and especially Corporate IT and more in special people with a vague (in the eyes of the business) function as Enterprise Architect are at least partly but more often largely disconnected of the business world (or vice versa). So yes, indeed you should try to develop some ‘grand design’, but probably the main requirement for such a grand design is the ability to deal with change and (evolutionary) development of requirements. Deliver and deliver fast in line with actual requirements is key to build confidence in your good intentions. Your attitude should be looking for “the yes reasons” and ways to cooperate and not looking for “the no reasons” to wait , delay or do it really different.</description>
		<content:encoded><![CDATA[<p>This is a real ‘chicken and egg’ problem in any somewhat larger organization. Business governance is often shared across and within several functional and/or geographical business units. Each of these units has its own needs, agenda en funds. IT and especially Corporate IT and more in special people with a vague (in the eyes of the business) function as Enterprise Architect are at least partly but more often largely disconnected of the business world (or vice versa). So yes, indeed you should try to develop some ‘grand design’, but probably the main requirement for such a grand design is the ability to deal with change and (evolutionary) development of requirements. Deliver and deliver fast in line with actual requirements is key to build confidence in your good intentions. Your attitude should be looking for “the yes reasons” and ways to cooperate and not looking for “the no reasons” to wait , delay or do it really different.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
