<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.1.3" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Business Process Modeling - Need and Approach</title>
	<link>http://www.ebizvitals.com/blog/2007/04/30/business-process-modeling-need-and-approach/</link>
	<description>Practical BPM thinking and application</description>
	<pubDate>Thu, 09 Sep 2010 10:20:46 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.1.3</generator>

	<item>
		<title>By: Ankur Srivastava</title>
		<link>http://www.ebizvitals.com/blog/2007/04/30/business-process-modeling-need-and-approach/#comment-4</link>
		<author>Ankur Srivastava</author>
		<pubDate>Tue, 01 May 2007 11:07:16 +0000</pubDate>
		<guid>http://www.ebizvitals.com/blog/2007/04/30/business-process-modeling-need-and-approach/#comment-4</guid>
					<description>Pretty interesting observation about "standards" being a pre-requisite for process modelling. I have experienced first hand a full blown collision of Modelling standards not only across projects in different business units in an organisation but within the same programme of a business unit!  The issue is that not too many business analysts and process engineers feel comfortable modelling in a manner they are not used to. Organisations should ideally rely on Business Architects to adopt a de facto standard. Unlike technology platform being standardised in organisations, modelling techniques have still along way to go before they achieve the same level of maturity from a standards perspective. Any tips to facilitate the formalizing modelling standards?</description>
		<content:encoded><![CDATA[<p>Pretty interesting observation about &#8220;standards&#8221; being a pre-requisite for process modelling. I have experienced first hand a full blown collision of Modelling standards not only across projects in different business units in an organisation but within the same programme of a business unit! The issue is that not too many business analysts and process engineers feel comfortable modelling in a manner they are not used to. Organisations should ideally rely on Business Architects to adopt a de facto standard. Unlike technology platform being standardised in organisations, modelling techniques have still along way to go before they achieve the same level of maturity from a standards perspective. Any tips to facilitate the formalizing modelling standards?</p>
]]></content:encoded>
				</item>
	<item>
		<title>By: Mark McGregor</title>
		<link>http://www.ebizvitals.com/blog/2007/04/30/business-process-modeling-need-and-approach/#comment-33</link>
		<author>Mark McGregor</author>
		<pubDate>Tue, 12 Jun 2007 11:18:25 +0000</pubDate>
		<guid>http://www.ebizvitals.com/blog/2007/04/30/business-process-modeling-need-and-approach/#comment-33</guid>
					<description>Lots of good things in this piece, however I disagree with the position on the need for process standards. Experience shows that the people who care about standards fall into two categories. Firstly vendors, because it saves them development costs and makes it easier for them to market to other peoples user bases. Secondly, it is IT people who of course are less interested in the business model and instead are looking to turn models into programs. In my experience it is very rare for the overhead of process notations to actually add real value to the business. 

While business process mapping or modeling is an important part of an improvement exercise it must always be remembered that the purpose is to help solve a genuine business problem. In which case the "just enough" approach is paramount and this usually does not require in depth business process models. 

My suggestion is that we do not confuse the needs of a business with teh needs of IT people who are building systems (these latter people will benefit from a standard)</description>
		<content:encoded><![CDATA[<p>Lots of good things in this piece, however I disagree with the position on the need for process standards. Experience shows that the people who care about standards fall into two categories. Firstly vendors, because it saves them development costs and makes it easier for them to market to other peoples user bases. Secondly, it is IT people who of course are less interested in the business model and instead are looking to turn models into programs. In my experience it is very rare for the overhead of process notations to actually add real value to the business. </p>
<p>While business process mapping or modeling is an important part of an improvement exercise it must always be remembered that the purpose is to help solve a genuine business problem. In which case the &#8220;just enough&#8221; approach is paramount and this usually does not require in depth business process models. </p>
<p>My suggestion is that we do not confuse the needs of a business with teh needs of IT people who are building systems (these latter people will benefit from a standard)</p>
]]></content:encoded>
				</item>
</channel>
</rss>
