<?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: Application Development 2.0</title>
	<atom:link href="http://jtonedm.com/2008/07/30/application-development-20/feed/" rel="self" type="application/rss+xml" />
	<link>http://jtonedm.com/2008/07/30/application-development-20/</link>
	<description>James Taylor on Everything Decision Management</description>
	<lastBuildDate>Sun, 21 Mar 2010 19:03:55 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Some thoughts on perfect application development — JT on EDM</title>
		<link>http://jtonedm.com/2008/07/30/application-development-20/comment-page-1/#comment-19358</link>
		<dc:creator>Some thoughts on perfect application development — JT on EDM</dc:creator>
		<pubDate>Wed, 10 Mar 2010 20:56:03 +0000</pubDate>
		<guid isPermaLink="false">http://jtonedm.com/?p=517#comment-19358</guid>
		<description>[...] have blogged before about Application Development 2.0 as well as the power of business rules in model-driven development/agile and the ways in which [...]</description>
		<content:encoded><![CDATA[<p>[...] have blogged before about Application Development 2.0 as well as the power of business rules in model-driven development/agile and the ways in which [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Taylor's Decision Management</title>
		<link>http://jtonedm.com/2008/07/30/application-development-20/comment-page-1/#comment-14626</link>
		<dc:creator>James Taylor's Decision Management</dc:creator>
		<pubDate>Wed, 22 Jul 2009 19:41:39 +0000</pubDate>
		<guid isPermaLink="false">http://jtonedm.com/?p=517#comment-14626</guid>
		<description>&lt;strong&gt;Getting business and IT alignment with business rules...&lt;/strong&gt;

Michael Cote of Redmonk had a nice piece on over on his People over Process blog. He made a series of great points about the risk of business and IT people not being aligned - risks to the business and......</description>
		<content:encoded><![CDATA[<p><strong>Getting business and IT alignment with business rules&#8230;</strong></p>
<p>Michael Cote of Redmonk had a nice piece on over on his People over Process blog. He made a series of great points about the risk of business and IT people not being aligned &#8211; risks to the business and&#8230;&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Taylor's Decision Management</title>
		<link>http://jtonedm.com/2008/07/30/application-development-20/comment-page-1/#comment-14606</link>
		<dc:creator>James Taylor's Decision Management</dc:creator>
		<pubDate>Mon, 20 Jul 2009 20:32:13 +0000</pubDate>
		<guid isPermaLink="false">http://jtonedm.com/?p=517#comment-14606</guid>
		<description>&lt;strong&gt;Is the Speed of Decision Making Accelerating? Yes...&lt;/strong&gt;

Paul Brasch wrote a nice piece on Is the Speed of Decision Making Accelerating. He concludes, and I agree, that it is in fact doing so - the need to decide while customers are on the phone or on the......</description>
		<content:encoded><![CDATA[<p><strong>Is the Speed of Decision Making Accelerating? Yes&#8230;</strong></p>
<p>Paul Brasch wrote a nice piece on Is the Speed of Decision Making Accelerating. He concludes, and I agree, that it is in fact doing so &#8211; the need to decide while customers are on the phone or on the&#8230;&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Application Development 2.0 &#124; Patrick Verbruggen's Blog</title>
		<link>http://jtonedm.com/2008/07/30/application-development-20/comment-page-1/#comment-11248</link>
		<dc:creator>Application Development 2.0 &#124; Patrick Verbruggen's Blog</dc:creator>
		<pubDate>Thu, 18 Sep 2008 18:02:42 +0000</pubDate>
		<guid isPermaLink="false">http://jtonedm.com/?p=517#comment-11248</guid>
		<description>[...] James Taylor makes interesting statements regarding Application Development 2.0: [...]</description>
		<content:encoded><![CDATA[<p>[...] James Taylor makes interesting statements regarding Application Development 2.0: [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Paker</title>
		<link>http://jtonedm.com/2008/07/30/application-development-20/comment-page-1/#comment-10869</link>
		<dc:creator>Kevin Paker</dc:creator>
		<pubDate>Sun, 07 Sep 2008 17:20:51 +0000</pubDate>
		<guid isPermaLink="false">http://jtonedm.com/?p=517#comment-10869</guid>
		<description>The business analyst is going to become the critical fulcrum between lines of business and IT. Their role will change in an umber of ways and will grow to include:

o Directing IT to create enablement and empowerment through the creation of a business-centric SOA strategy that puts service and technologies that consume those services in the hands of the business

o Creating complete and prototype applications on behalf of the business that the business then modify and enrich over time

o Prioritizing the work in IT so that business critical tasks are addressed in a timely manner.

All of this is going to mean extending the ALM processes and tools out of IT and into the business with the same rigor and diligence as exists in App Dev today but without the over complex and user unfriendly usabilities issues. A new breed of Office-like tools that naturally do version control, configuration management, approvals, deployments and backouts (etc.) are emerging that users are at ease with and which integrate well with IT&#039;s own tools for doing the same.

The focus of App Dev tools needs to shift to the business.</description>
		<content:encoded><![CDATA[<p>The business analyst is going to become the critical fulcrum between lines of business and IT. Their role will change in an umber of ways and will grow to include:</p>
<p>o Directing IT to create enablement and empowerment through the creation of a business-centric SOA strategy that puts service and technologies that consume those services in the hands of the business</p>
<p>o Creating complete and prototype applications on behalf of the business that the business then modify and enrich over time</p>
<p>o Prioritizing the work in IT so that business critical tasks are addressed in a timely manner.</p>
<p>All of this is going to mean extending the ALM processes and tools out of IT and into the business with the same rigor and diligence as exists in App Dev today but without the over complex and user unfriendly usabilities issues. A new breed of Office-like tools that naturally do version control, configuration management, approvals, deployments and backouts (etc.) are emerging that users are at ease with and which integrate well with IT&#8217;s own tools for doing the same.</p>
<p>The focus of App Dev tools needs to shift to the business.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The role of decision management in creating (and maintaining a common vision &#187; Smart )</title>
		<link>http://jtonedm.com/2008/07/30/application-development-20/comment-page-1/#comment-10852</link>
		<dc:creator>The role of decision management in creating (and maintaining a common vision &#187; Smart )</dc:creator>
		<pubDate>Wed, 03 Sep 2008 16:39:01 +0000</pubDate>
		<guid isPermaLink="false">http://jtonedm.com/?p=517#comment-10852</guid>
		<description>[...] An interesting article on the role of the business analyst in creating a common vision caught my eye this morning. The article focused on creating a common vision but it made me think about maintaining and developing that common vision over time, particularly of the complex logic in a system. Procedural code does not lend itself to business user understanding and I am not convinced there is that much a business analyst can do to help. If, however, the complex logic is externalized as a decision and that decision is managed declaratively (using business rules, say) then the business analyst (and the business user) have a viable point of communication with the programmers. Whether the non-technical users maintain the rules directly or collaborate with programmers to make the changes they need, the separation of business logic from &#8220;plumbing&#8221; code and the use of a declarative, higher-level syntax mean they will be much more likely to maintain a common vision of the system&#8217;s behavior. As I have said before, we could call this application development 2.0. [...]</description>
		<content:encoded><![CDATA[<p>[...] An interesting article on the role of the business analyst in creating a common vision caught my eye this morning. The article focused on creating a common vision but it made me think about maintaining and developing that common vision over time, particularly of the complex logic in a system. Procedural code does not lend itself to business user understanding and I am not convinced there is that much a business analyst can do to help. If, however, the complex logic is externalized as a decision and that decision is managed declaratively (using business rules, say) then the business analyst (and the business user) have a viable point of communication with the programmers. Whether the non-technical users maintain the rules directly or collaborate with programmers to make the changes they need, the separation of business logic from &#8220;plumbing&#8221; code and the use of a declarative, higher-level syntax mean they will be much more likely to maintain a common vision of the system&#8217;s behavior. As I have said before, we could call this application development 2.0. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Application Development 2.0 &#124; .</title>
		<link>http://jtonedm.com/2008/07/30/application-development-20/comment-page-1/#comment-10760</link>
		<dc:creator>Application Development 2.0 &#124; .</dc:creator>
		<pubDate>Fri, 15 Aug 2008 14:12:48 +0000</pubDate>
		<guid isPermaLink="false">http://jtonedm.com/?p=517#comment-10760</guid>
		<description>[...] Application Development 2.0 [...]</description>
		<content:encoded><![CDATA[<p>[...] Application Development 2.0 [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Link Builder</title>
		<link>http://jtonedm.com/2008/07/30/application-development-20/comment-page-1/#comment-10668</link>
		<dc:creator>Link Builder</dc:creator>
		<pubDate>Tue, 05 Aug 2008 03:54:13 +0000</pubDate>
		<guid isPermaLink="false">http://jtonedm.com/?p=517#comment-10668</guid>
		<description>Nice thread. This article should aid the lack of application developer. Minimizes the gap between end users and the programmers.</description>
		<content:encoded><![CDATA[<p>Nice thread. This article should aid the lack of application developer. Minimizes the gap between end users and the programmers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: A reader asks&#8230; about development, business rules and model-driven development &#187; Smart (Enough Systems, the blog)</title>
		<link>http://jtonedm.com/2008/07/30/application-development-20/comment-page-1/#comment-10667</link>
		<dc:creator>A reader asks&#8230; about development, business rules and model-driven development &#187; Smart (Enough Systems, the blog)</dc:creator>
		<pubDate>Tue, 05 Aug 2008 01:16:22 +0000</pubDate>
		<guid isPermaLink="false">http://jtonedm.com/?p=517#comment-10667</guid>
		<description>[...] on the topic. Personally I think the Agile approach works especially well as I said in my recent Application Development 2.0 post. To repeat an article I wrote on agile business rules, I find the use of business rules to be [...]</description>
		<content:encoded><![CDATA[<p>[...] on the topic. Personally I think the Agile approach works especially well as I said in my recent Application Development 2.0 post. To repeat an article I wrote on agile business rules, I find the use of business rules to be [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lucas Rodriguez Cervera</title>
		<link>http://jtonedm.com/2008/07/30/application-development-20/comment-page-1/#comment-10635</link>
		<dc:creator>Lucas Rodriguez Cervera</dc:creator>
		<pubDate>Thu, 31 Jul 2008 05:59:23 +0000</pubDate>
		<guid isPermaLink="false">http://jtonedm.com/?p=517#comment-10635</guid>
		<description>I completely agree with using business rules in application development as a way to introduce agility in your operations.
I also see a lot of value in having users involved in QA and requirements specification, but the the difficulty lies in engaging people so much that they are interested in helping you. You need   a criticall mass of users to achive what facebook did, for example, with its translations.</description>
		<content:encoded><![CDATA[<p>I completely agree with using business rules in application development as a way to introduce agility in your operations.<br />
I also see a lot of value in having users involved in QA and requirements specification, but the the difficulty lies in engaging people so much that they are interested in helping you. You need   a criticall mass of users to achive what facebook did, for example, with its translations.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->