<?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>Bob Lambert &#187; Business Analysis</title>
	<atom:link href="http://robertlambert.net/tag/business-analysis/feed/" rel="self" type="application/rss+xml" />
	<link>http://robertlambert.net</link>
	<description>on business-aligned information technology</description>
	<lastBuildDate>Fri, 20 Jan 2012 21:05:57 +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>Abstracting and recombining all the way to the bank</title>
		<link>http://robertlambert.net/2011/08/abstracting-and-recombining-all-the-way-to-the-bank/</link>
		<comments>http://robertlambert.net/2011/08/abstracting-and-recombining-all-the-way-to-the-bank/#comments</comments>
		<pubDate>Tue, 30 Aug 2011 14:32:34 +0000</pubDate>
		<dc:creator>Bob</dc:creator>
				<category><![CDATA[Analysis]]></category>
		<category><![CDATA[App Dev]]></category>
		<category><![CDATA[Business]]></category>
		<category><![CDATA[Alignment]]></category>
		<category><![CDATA[Business Analysis]]></category>
		<category><![CDATA[Business Intelligence]]></category>
		<category><![CDATA[Data Modeling]]></category>
		<category><![CDATA[Database Design]]></category>
		<category><![CDATA[Strategy]]></category>

		<guid isPermaLink="false">http://robertlambert.net/?p=1208</guid>
		<description><![CDATA[In the past I&#8217;ve never understood what people really mean they say &#8220;think outside the box&#8221; but Jim Harris, in a recent OCDQ blog post, helped me figure it out. Mr. Harris ends with this provocative line: &#8220;the bottom line is Google and Facebook have socialized data in order to capitalize data as a true corporate asset.&#8221;  The post <a href='http://robertlambert.net/2011/08/abstracting-and-recombining-all-the-way-to-the-bank/'>[...]</a>]]></description>
		<wfw:commentRss>http://robertlambert.net/2011/08/abstracting-and-recombining-all-the-way-to-the-bank/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Get an early start for on-time data modeling</title>
		<link>http://robertlambert.net/2011/07/get-an-early-start-for-on-time-data-modeling/</link>
		<comments>http://robertlambert.net/2011/07/get-an-early-start-for-on-time-data-modeling/#comments</comments>
		<pubDate>Fri, 22 Jul 2011 22:14:39 +0000</pubDate>
		<dc:creator>Bob</dc:creator>
				<category><![CDATA[Analysis]]></category>
		<category><![CDATA[App Dev]]></category>
		<category><![CDATA[Data Management]]></category>
		<category><![CDATA[IT]]></category>
		<category><![CDATA[Project Management]]></category>
		<category><![CDATA[Business Analysis]]></category>
		<category><![CDATA[Data Modeling]]></category>
		<category><![CDATA[Database Design]]></category>
		<category><![CDATA[Requirements]]></category>

		<guid isPermaLink="false">http://robertlambert.net/?p=1201</guid>
		<description><![CDATA[I&#8217;m a data modeler, so I enjoyed Jonathon Geiger&#8217;s recent article entitled &#8220;Why Does Data Modeling Take So Long&#8221;.  But why does he say it like it&#8217;s a bad thing? Mr. Geiger&#8217;s bottom line is exactly right: &#8220;Most of the time spent developing data models is consumed developing or clarifying the requirements and business rules <a href='http://robertlambert.net/2011/07/get-an-early-start-for-on-time-data-modeling/'>[...]</a>]]></description>
		<wfw:commentRss>http://robertlambert.net/2011/07/get-an-early-start-for-on-time-data-modeling/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Building a writing culture in application development</title>
		<link>http://robertlambert.net/2011/01/building-a-writing-culture-in-application-development/</link>
		<comments>http://robertlambert.net/2011/01/building-a-writing-culture-in-application-development/#comments</comments>
		<pubDate>Mon, 24 Jan 2011 02:26:55 +0000</pubDate>
		<dc:creator>Bob</dc:creator>
				<category><![CDATA[App Dev]]></category>
		<category><![CDATA[Business]]></category>
		<category><![CDATA[IT]]></category>
		<category><![CDATA[Project Management]]></category>
		<category><![CDATA[Alignment]]></category>
		<category><![CDATA[Business Analysis]]></category>
		<category><![CDATA[Leading & Following]]></category>

		<guid isPermaLink="false">http://robertlambert.net/?p=1101</guid>
		<description><![CDATA[One of the key skills needed in today&#8217;s IT shop is communication, and one of the best ways to improve ability to communicate is to write blog posts and articles. In spite of &#8220;IT guy&#8221; stereotypes, communication and analytical thinking about business are among the most important skills in application development. Developers, analysts, and managers <a href='http://robertlambert.net/2011/01/building-a-writing-culture-in-application-development/'>[...]</a>]]></description>
		<wfw:commentRss>http://robertlambert.net/2011/01/building-a-writing-culture-in-application-development/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Agile development: rugby analogy considered harmful</title>
		<link>http://robertlambert.net/2010/12/agile-development-rugby-analogy-considered-harmful/</link>
		<comments>http://robertlambert.net/2010/12/agile-development-rugby-analogy-considered-harmful/#comments</comments>
		<pubDate>Mon, 13 Dec 2010 17:53:39 +0000</pubDate>
		<dc:creator>Bob</dc:creator>
				<category><![CDATA[App Dev]]></category>
		<category><![CDATA[IT]]></category>
		<category><![CDATA[Project Management]]></category>
		<category><![CDATA[agile]]></category>
		<category><![CDATA[Alignment]]></category>
		<category><![CDATA[Business Analysis]]></category>
		<category><![CDATA[Business Case]]></category>
		<category><![CDATA[Requirements]]></category>

		<guid isPermaLink="false">http://robertlambert.net/?p=1037</guid>
		<description><![CDATA[Recently my friend Mark Hudson posted about the inappropriateness of the term &#8220;sprint&#8221; for an agile project phase, preferring the cycling term &#8220;interval.&#8221; That post really struck a chord with me. As a rugby union fan and former wing/fullback I&#8217;ve always thought the whole rugby analogy was wrong. Agile development is continuous and fluid, yet <a href='http://robertlambert.net/2010/12/agile-development-rugby-analogy-considered-harmful/'>[...]</a>]]></description>
		<wfw:commentRss>http://robertlambert.net/2010/12/agile-development-rugby-analogy-considered-harmful/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Use conceptual data modeling in requirements definition</title>
		<link>http://robertlambert.net/2010/07/use-conceptual-data-modeling-in-requirements-definition/</link>
		<comments>http://robertlambert.net/2010/07/use-conceptual-data-modeling-in-requirements-definition/#comments</comments>
		<pubDate>Fri, 16 Jul 2010 16:24:50 +0000</pubDate>
		<dc:creator>Bob</dc:creator>
				<category><![CDATA[Analysis]]></category>
		<category><![CDATA[App Dev]]></category>
		<category><![CDATA[IT]]></category>
		<category><![CDATA[Project Management]]></category>
		<category><![CDATA[Business Analysis]]></category>
		<category><![CDATA[Data Modeling]]></category>
		<category><![CDATA[Database Design]]></category>
		<category><![CDATA[Requirements]]></category>

		<guid isPermaLink="false">http://robertlambert.net/?p=979</guid>
		<description><![CDATA[I’ve often thought that conceptual data modeling was an underused tool in the arsenal available to requirements analysts, and in a recent conversation I found that many were surprised that it would be used in the requirements phase at all.  Checking the Business Analysis Body of Knowledge (BABOK) I found data modeling listed among the <a href='http://robertlambert.net/2010/07/use-conceptual-data-modeling-in-requirements-definition/'>[...]</a>]]></description>
		<wfw:commentRss>http://robertlambert.net/2010/07/use-conceptual-data-modeling-in-requirements-definition/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>SQL Saturday #30, Richmond Virginia, April 10, 2010</title>
		<link>http://robertlambert.net/2010/04/sql-saturday-30-richmond-virginia-april-10-2010/</link>
		<comments>http://robertlambert.net/2010/04/sql-saturday-30-richmond-virginia-april-10-2010/#comments</comments>
		<pubDate>Fri, 09 Apr 2010 16:44:06 +0000</pubDate>
		<dc:creator>Bob</dc:creator>
				<category><![CDATA[IT]]></category>
		<category><![CDATA[Business Analysis]]></category>
		<category><![CDATA[Data Management]]></category>
		<category><![CDATA[Data Modeling]]></category>
		<category><![CDATA[Database Design]]></category>
		<category><![CDATA[Requirements]]></category>

		<guid isPermaLink="false">http://robertlambert.net/?p=900</guid>
		<description><![CDATA[Thanks to all who attended my presentations at SQL Saturday on April 10.  Here are the materials from my two presentations: - The Business End of Data Modeling (2.5m powerpoint presentation) - Normalize Metadata For Data Integration Analysis (5.5m full version, zip including presentation and code samples) - Normalize Metadata For Data Integration Analysis (small) <a href='http://robertlambert.net/2010/04/sql-saturday-30-richmond-virginia-april-10-2010/'>[...]</a>]]></description>
		<wfw:commentRss>http://robertlambert.net/2010/04/sql-saturday-30-richmond-virginia-april-10-2010/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Business requirements up front</title>
		<link>http://robertlambert.net/2010/03/plan-decide-ac/</link>
		<comments>http://robertlambert.net/2010/03/plan-decide-ac/#comments</comments>
		<pubDate>Wed, 31 Mar 2010 20:38:03 +0000</pubDate>
		<dc:creator>Bob</dc:creator>
				<category><![CDATA[IT]]></category>
		<category><![CDATA[Alignment]]></category>
		<category><![CDATA[Business Analysis]]></category>
		<category><![CDATA[Business Case]]></category>
		<category><![CDATA[Project Management]]></category>
		<category><![CDATA[Requirements]]></category>
		<category><![CDATA[Strategy]]></category>

		<guid isPermaLink="false">http://robertlambert.net/?p=866</guid>
		<description><![CDATA[&#8220;Our goals can only be reached through a vehicle of a plan, in which we must fervently believe, and upon which we must vigorously act. There is no other route to success.&#8221; &#8211; Pablo Picasso It is an old story: about 30% of IT application projects succeed, 45% are &#8220;challenged,&#8221; and the other quarter fail <a href='http://robertlambert.net/2010/03/plan-decide-ac/'>[...]</a>]]></description>
		<wfw:commentRss>http://robertlambert.net/2010/03/plan-decide-ac/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Study data early to improve application alignment</title>
		<link>http://robertlambert.net/2009/05/study-data-early-to-improve-application-alignment/</link>
		<comments>http://robertlambert.net/2009/05/study-data-early-to-improve-application-alignment/#comments</comments>
		<pubDate>Mon, 11 May 2009 21:26:52 +0000</pubDate>
		<dc:creator>Bob</dc:creator>
				<category><![CDATA[Data Management]]></category>
		<category><![CDATA[IT]]></category>
		<category><![CDATA[Project Management]]></category>
		<category><![CDATA[Alignment]]></category>
		<category><![CDATA[Business Analysis]]></category>
		<category><![CDATA[Requirements]]></category>

		<guid isPermaLink="false">http://robertlambert.net/?p=447</guid>
		<description><![CDATA[A recurring theme in the literature on IT over the years has been frequent failure of IT projects.  Most studies lay the bulk of the blame on requirements (examples here and here).  One way to improve accuracy and fit-to-purpose of requirements, and thereby promote project success, is to include data analysis as well as process <a href='http://robertlambert.net/2009/05/study-data-early-to-improve-application-alignment/'>[...]</a>]]></description>
		<wfw:commentRss>http://robertlambert.net/2009/05/study-data-early-to-improve-application-alignment/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>No business value in nulls</title>
		<link>http://robertlambert.net/2009/04/no-business-value-in-nulls/</link>
		<comments>http://robertlambert.net/2009/04/no-business-value-in-nulls/#comments</comments>
		<pubDate>Sun, 05 Apr 2009 22:10:43 +0000</pubDate>
		<dc:creator>Bob</dc:creator>
				<category><![CDATA[Analysis]]></category>
		<category><![CDATA[Data Management]]></category>
		<category><![CDATA[IT]]></category>
		<category><![CDATA[Business Analysis]]></category>
		<category><![CDATA[Data Modeling]]></category>
		<category><![CDATA[Database Design]]></category>

		<guid isPermaLink="false">http://robertlambert.net/?p=345</guid>
		<description><![CDATA[It seems I&#8217;m frequently in conversations about using null to represent a business value.  To paraphrase, say there are credit and cash customers, and there&#8217;s a suggestion to set &#8220;Customer_Type&#8221; to &#8220;C&#8221; for credit and null for cash.  To data and database professionals this is obviously a bad idea, but it&#8217;s not obvious from a <a href='http://robertlambert.net/2009/04/no-business-value-in-nulls/'>[...]</a>]]></description>
		<wfw:commentRss>http://robertlambert.net/2009/04/no-business-value-in-nulls/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>A pretty good requirements analysis checklist</title>
		<link>http://robertlambert.net/2009/02/requirements-analysis-plan/</link>
		<comments>http://robertlambert.net/2009/02/requirements-analysis-plan/#comments</comments>
		<pubDate>Fri, 13 Feb 2009 10:16:31 +0000</pubDate>
		<dc:creator>Bob</dc:creator>
				<category><![CDATA[Analysis]]></category>
		<category><![CDATA[IT]]></category>
		<category><![CDATA[Project Management]]></category>
		<category><![CDATA[Business Analysis]]></category>
		<category><![CDATA[Requirements]]></category>

		<guid isPermaLink="false">http://robertlambert.net/?p=58</guid>
		<description><![CDATA[Recently I was asked for a high level requirements plan for a large IT conversion.  I googled around a little for something standard.  I found some good references (see links at the bottom of this post), but not exactly what I was looking for: a simple, method-agnostic layout of the high level steps and checkpoints <a href='http://robertlambert.net/2009/02/requirements-analysis-plan/'>[...]</a>]]></description>
		<wfw:commentRss>http://robertlambert.net/2009/02/requirements-analysis-plan/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

