<?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"
	>
<channel>
	<title>Comments on: The Springboard Twist: Deductive Business Logic</title>
	<atom:link href="http://www.springboard-software.com/2006/06/20/the-springboard-twist-deductive-business-logic/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.springboard-software.com/2006/06/20/the-springboard-twist-deductive-business-logic/</link>
	<description>Web Development With a Twist</description>
	<pubDate>Sat, 22 Nov 2008 05:26:40 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Michael</title>
		<link>http://www.springboard-software.com/2006/06/20/the-springboard-twist-deductive-business-logic/#comment-3</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Thu, 22 Jun 2006 15:39:42 +0000</pubDate>
		<guid isPermaLink="false">http://blog.springboard-software.com/?p=8#comment-3</guid>
		<description>Good question.  The first thing I would submit is that you're not likely to map business vision to any actions if you have failed to articulate what your vision is in the first place.  In an ideal world, project sponsors would have a clear vision of what they hope to accomplish before starting any development work.  Often, however, there's plenty of development work prior to the definition of what the business goals for the work are.

So - before we worry about the next steps, we need to make sure we've taken the first steps toward articulating our business vision for a project.  This can be done after the project has started though it's better to do it early in the project's inception phase.  Doing this later in the project also may involve changes to the overall project scope, which puts the whole shebang at risk. 
</description>
		<content:encoded><![CDATA[<p>Good question.  The first thing I would submit is that you&#8217;re not likely to map business vision to any actions if you have failed to articulate what your vision is in the first place.  In an ideal world, project sponsors would have a clear vision of what they hope to accomplish before starting any development work.  Often, however, there&#8217;s plenty of development work prior to the definition of what the business goals for the work are.</p>
<p>So - before we worry about the next steps, we need to make sure we&#8217;ve taken the first steps toward articulating our business vision for a project.  This can be done after the project has started though it&#8217;s better to do it early in the project&#8217;s inception phase.  Doing this later in the project also may involve changes to the overall project scope, which puts the whole shebang at risk.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: grp</title>
		<link>http://www.springboard-software.com/2006/06/20/the-springboard-twist-deductive-business-logic/#comment-2</link>
		<dc:creator>grp</dc:creator>
		<pubDate>Thu, 22 Jun 2006 12:20:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.springboard-software.com/?p=8#comment-2</guid>
		<description>Then what? How do you take the next step in business mapping of vision to action? An example would be nice.</description>
		<content:encoded><![CDATA[<p>Then what? How do you take the next step in business mapping of vision to action? An example would be nice.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
