<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:blogger="http://schemas.google.com/blogger/2008" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr="http://purl.org/syndication/thread/1.0" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" gd:etag="W/&quot;D0MMQ3Y-fCp7ImA9WhFSE0U.&quot;"><id>tag:blogger.com,1999:blog-4560463190032436692</id><updated>2013-06-16T14:24:42.854+02:00</updated><category term="PEAS" /><category term="business architecture" /><category term="workflow" /><category term="enterprise architecture" /><category term="architect enterprise BPM systems" /><category term="e-gov" /><category term="terminology" /><category term="systems thinking" /><category term="enterprise patterns" /><category term="agility" /><category term="SOA" /><category term="service" /><category term="BPMS" /><category term="book about BPM SOA EA" /><category term="practical process patterns" /><category term="PMO" /><category term="SAP" /><category term="e-Tunisia" /><category term="e-government" /><category term="process orchestration" /><category term="From vendor-centric BPM to customer-centric BPM" /><category term="PI" /><category term="EPN" /><category term="NetWeaver" /><category term="EA" /><category term="enterprise business perfomance" /><category term="PLM" /><category term="#bizarch" /><category term="ACM" /><category term="SDLC" /><category term="BA" /><category term="process" /><category term="outside-in" /><category term="e-governance" /><category term="security" /><category term="OMG" /><category term="example" /><category term="KPI" /><category term="BPM reference model" /><category term="IT strategy" /><category term="BPM" /><category term="flexibily" /><category term="cloud" /><category term="ERM" /><category term="PMI" /><category term="SLA" /><category term="ITIL" /><category term="africa" /><category term="SAPTech2012" /><category term="case management" /><category term="e-Tunisie" /><category term="integration" /><category term="BPMN" /><category term="architect" /><category term="process choreography" /><category term="Intalio" /><category term="automation" /><category term="architecture" /><category term="virtualisation" /><category term="BPM standards" /><category term="data" /><category term="CMMI" /><category term="modelling procedure" /><title>Improving Enterprise Business Process Management Systems</title><subtitle type="html">This blog complements the support web site for my book "Improving enterprise business process management systems" about BPM, SOA and EA, which has just been published (see www.improving-BPM-systems.com/book ).</subtitle><link rel="http://schemas.google.com/g/2005#feed" type="application/atom+xml" href="http://improving-bpm-systems.blogspot.com/feeds/posts/default" /><link rel="alternate" type="text/html" href="http://improving-bpm-systems.blogspot.com/" /><link rel="next" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default?start-index=26&amp;max-results=25&amp;redirect=false&amp;v=2" /><author><name>Alexander SAMARIN</name><uri>https://plus.google.com/112810118258856486156</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-rb1Di6vctuI/AAAAAAAAAAI/AAAAAAAABJQ/gFbMGYq7mqI/s512-c/photo.jpg" /></author><generator version="7.00" uri="http://www.blogger.com">Blogger</generator><openSearch:totalResults>217</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/atom+xml" href="http://feeds.feedburner.com/ImprovingEnterpriseBusinessProcessManagementSystems" /><feedburner:info uri="improvingenterprisebusinessprocessmanagementsystems" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><feedburner:emailServiceId>ImprovingEnterpriseBusinessProcessManagementSystems</feedburner:emailServiceId><feedburner:feedburnerHostname>http://feedburner.google.com</feedburner:feedburnerHostname><entry gd:etag="W/&quot;DEcDQHgzfyp7ImA9WhFSEUQ.&quot;"><id>tag:blogger.com,1999:blog-4560463190032436692.post-8143605102022761753</id><published>2013-06-14T09:47:00.002+02:00</published><updated>2013-06-14T09:47:51.687+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-06-14T09:47:51.687+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="#bizarch" /><category scheme="http://www.blogger.com/atom/ns#" term="business architecture" /><category scheme="http://www.blogger.com/atom/ns#" term="BA" /><title>#bizarch artefacts concept map</title><summary type="html">This blogpost accumulates my contribution (it is work in progress) into LinkedIn discussion "
Business capability concepts map" http://www.linkedin.com/groupAnswers?viewQuestionAndAnswers=&amp;amp;discussionID=245602764&amp;amp;gid=84758&amp;amp;commentID=144209821&amp;amp;trk=view_disc&amp;amp;ut=0BMR0Vl690JBM1

The reference blogpost is http://improving-bpm-systems.blogspot.com/2013/03/bizarch-artefacts-definition-again.html  I use &lt;img src="http://feeds.feedburner.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~4/uGBX6wuTkq0" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://improving-bpm-systems.blogspot.com/feeds/8143605102022761753/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=4560463190032436692&amp;postID=8143605102022761753" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/8143605102022761753?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/8143605102022761753?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~3/uGBX6wuTkq0/bizarch-artefacts-concept-map.html" title="#bizarch artefacts concept map" /><author><name>Alexander SAMARIN</name><uri>https://plus.google.com/112810118258856486156</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-rb1Di6vctuI/AAAAAAAAAAI/AAAAAAAABJQ/gFbMGYq7mqI/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://4.bp.blogspot.com/-1Wr0ZNzfOsA/UbrBcjBlODI/AAAAAAAABLw/xDx7AMzoTIM/s72-c/p2+(2).png" height="72" width="72" /><thr:total>0</thr:total><gd:extendedProperty name="commentSource" value="1" /><gd:extendedProperty name="commentModerationMode" value="FILTERED_POSTMOD" /><feedburner:origLink>http://improving-bpm-systems.blogspot.com/2013/06/bizarch-artefacts-concept-map.html</feedburner:origLink></entry><entry gd:etag="W/&quot;Ck4AQnkyfSp7ImA9WhFSEUQ.&quot;"><id>tag:blogger.com,1999:blog-4560463190032436692.post-2678043626684949748</id><published>2013-06-13T18:37:00.000+02:00</published><updated>2013-06-14T08:22:23.795+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-06-14T08:22:23.795+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="process" /><category scheme="http://www.blogger.com/atom/ns#" term="BPM" /><category scheme="http://www.blogger.com/atom/ns#" term="practical process patterns" /><title>Practical Process Patterns: Customer eXperience As A Process (CXAAP)</title><summary type="html">Another practical process pattern - Customer eXperience As A Process (CXAAP)

This blogpost is inspired by the sentence "The reason customers use our products and services, is to get jobs done in their lives." from http://bridging-the-gap.me/2013/06/03/designing-the-business-around-the-experience/

This sentence made me thinking about a hierarchy of embedded (in some sense) processes: 
"person's &lt;img src="http://feeds.feedburner.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~4/B1_9bRu4FN8" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://improving-bpm-systems.blogspot.com/feeds/2678043626684949748/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=4560463190032436692&amp;postID=2678043626684949748" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/2678043626684949748?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/2678043626684949748?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~3/B1_9bRu4FN8/practical-process-patterns-cxaap.html" title="Practical Process Patterns: Customer eXperience As A Process (CXAAP)" /><author><name>Alexander SAMARIN</name><uri>https://plus.google.com/112810118258856486156</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-rb1Di6vctuI/AAAAAAAAAAI/AAAAAAAABJQ/gFbMGYq7mqI/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://3.bp.blogspot.com/-AQ_o6vauiB4/UbnmUXwkuZI/AAAAAAAABLM/a5686oWozVA/s72-c/p1.png" height="72" width="72" /><thr:total>0</thr:total><gd:extendedProperty name="commentSource" value="1" /><gd:extendedProperty name="commentModerationMode" value="FILTERED_POSTMOD" /><feedburner:origLink>http://improving-bpm-systems.blogspot.com/2013/06/practical-process-patterns-cxaap.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUUESHk7eip7ImA9WhFTFU8.&quot;"><id>tag:blogger.com,1999:blog-4560463190032436692.post-6188999335382578332</id><published>2013-06-06T16:00:00.000+02:00</published><updated>2013-06-06T16:00:09.702+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-06-06T16:00:09.702+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="integration" /><category scheme="http://www.blogger.com/atom/ns#" term="enterprise patterns" /><title>Enterprise patterns: eclipse</title><summary type="html">This is actually the subclause 5.5 "Making coordination explicit" from my book www.samarin.biz/book

A typical enterprise IT landscape is a set of monolithic interactive applications. Such
applications usually have intra-application coordination in a very implicit way. Inter-application
coordination is also implemented but in an ad-hoc manner – some
changes of data stored in “Application A” &lt;img src="http://feeds.feedburner.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~4/wEOUdP3P-Gg" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://improving-bpm-systems.blogspot.com/feeds/6188999335382578332/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=4560463190032436692&amp;postID=6188999335382578332" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/6188999335382578332?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/6188999335382578332?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~3/wEOUdP3P-Gg/enterprise-patterns-eclipse.html" title="Enterprise patterns: eclipse" /><author><name>Alexander SAMARIN</name><uri>https://plus.google.com/112810118258856486156</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-rb1Di6vctuI/AAAAAAAAAAI/AAAAAAAABJQ/gFbMGYq7mqI/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://1.bp.blogspot.com/-Fel5WxmiILU/UbCUegItEHI/AAAAAAAABKk/54tOpQCGrh0/s72-c/p1.png" height="72" width="72" /><thr:total>0</thr:total><gd:extendedProperty name="commentSource" value="1" /><gd:extendedProperty name="commentModerationMode" value="FILTERED_POSTMOD" /><feedburner:origLink>http://improving-bpm-systems.blogspot.com/2013/06/enterprise-patterns-eclipse.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CkcMQnYzcSp7ImA9WhFTFEs.&quot;"><id>tag:blogger.com,1999:blog-4560463190032436692.post-1738677649667846978</id><published>2013-06-05T21:21:00.000+02:00</published><updated>2013-06-05T21:21:23.889+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-06-05T21:21:23.889+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="EA" /><title>#entarch basics in "for dummies" style</title><summary type="html">A fragment from a forthcoming article.




Why Enterprise Architecture? – To take right decisions on evolution

Any enterprise comprises many interrelated parts. Many people work for an enterprise; they must be managed; raw materials must be supplied in time; final products must be delivered as planned; enterprise’s goals must be achieved. All of those parts must be coordinated to work together &lt;img src="http://feeds.feedburner.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~4/Uq1kQ-yZcFo" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://improving-bpm-systems.blogspot.com/feeds/1738677649667846978/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=4560463190032436692&amp;postID=1738677649667846978" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/1738677649667846978?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/1738677649667846978?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~3/Uq1kQ-yZcFo/entarch-basics-in-for-dummies-style.html" title="#entarch basics in &quot;for dummies&quot; style" /><author><name>Alexander SAMARIN</name><uri>https://plus.google.com/112810118258856486156</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-rb1Di6vctuI/AAAAAAAAAAI/AAAAAAAABJQ/gFbMGYq7mqI/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://2.bp.blogspot.com/-0WXlGlOFYyk/Ua7cVCYRzaI/AAAAAAAABKQ/3iVkkHY24gI/s72-c/pic1.png" height="72" width="72" /><thr:total>0</thr:total><gd:extendedProperty name="commentSource" value="1" /><gd:extendedProperty name="commentModerationMode" value="FILTERED_POSTMOD" /><feedburner:origLink>http://improving-bpm-systems.blogspot.com/2013/06/entarch-basics-in-for-dummies-style.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEYARHc4cSp7ImA9WhFTE0s.&quot;"><id>tag:blogger.com,1999:blog-4560463190032436692.post-3240225175495783459</id><published>2013-05-31T21:51:00.000+02:00</published><updated>2013-06-04T19:15:45.939+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-06-04T19:15:45.939+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="service" /><category scheme="http://www.blogger.com/atom/ns#" term="integration" /><category scheme="http://www.blogger.com/atom/ns#" term="process" /><category scheme="http://www.blogger.com/atom/ns#" term="SOA" /><category scheme="http://www.blogger.com/atom/ns#" term="cloud" /><category scheme="http://www.blogger.com/atom/ns#" term="BPM" /><title>Integration via #BPM: become friendly to #cloud</title><summary type="html">This post was inspired by article "Cloud-Friendly BPM: the power of hypermedia-oriented architecture" from ZApThink available at http://www.zapthink.com/2013/05/21/cloud-friendly-bpm-the-power-of-hypermedia-oriented-architecture/ and, also "BPM and middleware vendors failing to adapt to the cloud – IDC" http://www.information-age.com/technology/cloud-and-virtualisation/123457063/&lt;img src="http://feeds.feedburner.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~4/TkAqTzmBKxc" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://improving-bpm-systems.blogspot.com/feeds/3240225175495783459/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=4560463190032436692&amp;postID=3240225175495783459" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/3240225175495783459?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/3240225175495783459?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~3/TkAqTzmBKxc/integration-via-bpm-become-friendly-to.html" title="Integration via #BPM: become friendly to #cloud" /><author><name>Alexander SAMARIN</name><uri>https://plus.google.com/112810118258856486156</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-rb1Di6vctuI/AAAAAAAAAAI/AAAAAAAABJQ/gFbMGYq7mqI/s512-c/photo.jpg" /></author><thr:total>0</thr:total><gd:extendedProperty name="commentSource" value="1" /><gd:extendedProperty name="commentModerationMode" value="FILTERED_POSTMOD" /><feedburner:origLink>http://improving-bpm-systems.blogspot.com/2013/05/integration-via-bpm-become-friendly-to.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUEGQ3k_cSp7ImA9WhBaGEk.&quot;"><id>tag:blogger.com,1999:blog-4560463190032436692.post-6501731455908921315</id><published>2013-05-29T19:13:00.004+02:00</published><updated>2013-05-29T19:13:42.749+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-05-29T19:13:42.749+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="enterprise architecture" /><title>Place of #entarch in an enterprise organisational chart</title><summary type="html">Based on the Linkedin discussion Should an Enterprise Architecture role report to the CEO?.

It depends (as usual). Place of EA should depend on the maturity of the whole organisation.

Low level - EA is under CIO 
Middle level - EA is under COO 
High level - EA is under CEO 
etc. 

Of course, there are extremes like an CIO saying: "Architecture? We don't need such a function. Everyone will do &lt;img src="http://feeds.feedburner.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~4/6bzRUURuUeI" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://improving-bpm-systems.blogspot.com/feeds/6501731455908921315/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=4560463190032436692&amp;postID=6501731455908921315" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/6501731455908921315?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/6501731455908921315?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~3/6bzRUURuUeI/place-of-entarch-in-enterprise.html" title="Place of #entarch in an enterprise organisational chart" /><author><name>Alexander SAMARIN</name><uri>https://plus.google.com/112810118258856486156</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-rb1Di6vctuI/AAAAAAAAAAI/AAAAAAAABJQ/gFbMGYq7mqI/s512-c/photo.jpg" /></author><thr:total>0</thr:total><gd:extendedProperty name="commentSource" value="1" /><gd:extendedProperty name="commentModerationMode" value="FILTERED_POSTMOD" /><feedburner:origLink>http://improving-bpm-systems.blogspot.com/2013/05/place-of-entarch-in-enterprise.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A0UFQHk8fyp7ImA9WhBbGUg.&quot;"><id>tag:blogger.com,1999:blog-4560463190032436692.post-1259257511411498781</id><published>2013-05-19T11:57:00.000+02:00</published><updated>2013-05-19T12:26:51.777+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-05-19T12:26:51.777+02:00</app:edited><title>My CV as a tweet</title><summary type="html">Architect #entarch+#bizarch+#BPM+#SOA+#ECM+#governance+#strategy for innovative transformations &amp;amp; better operations http://about.me/alexander.samarin

Thanks,
AS&lt;img src="http://feeds.feedburner.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~4/_hotgrPxejo" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://improving-bpm-systems.blogspot.com/feeds/1259257511411498781/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=4560463190032436692&amp;postID=1259257511411498781" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/1259257511411498781?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/1259257511411498781?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~3/_hotgrPxejo/my-cv-as-tweet.html" title="My CV as a tweet" /><author><name>Alexander SAMARIN</name><uri>https://plus.google.com/112810118258856486156</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-rb1Di6vctuI/AAAAAAAAAAI/AAAAAAAABJQ/gFbMGYq7mqI/s512-c/photo.jpg" /></author><thr:total>0</thr:total><gd:extendedProperty name="commentSource" value="1" /><gd:extendedProperty name="commentModerationMode" value="FILTERED_POSTMOD" /><feedburner:origLink>http://improving-bpm-systems.blogspot.com/2013/05/my-cv-as-tweet.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DkMNQ3g7eip7ImA9WhBVEU4.&quot;"><id>tag:blogger.com,1999:blog-4560463190032436692.post-6871089365894249488</id><published>2013-04-16T19:48:00.000+02:00</published><updated>2013-04-16T19:48:12.602+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-04-16T19:48:12.602+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="enterprise patterns" /><title>Enterprise patterns: Make Your Logic Obvious (MYLO)</title><summary type="html">This pattern is an underlining approach for several other enterprise patterns mentioned in the blog. It recommends making the decision logic as explicit as possible before approaching the decision itself. The logic must be understandable by all stakeholders of this decision. They should be able to execute this logic. So the logic will take the decision - not you. Thus explicit logic acts as a “&lt;img src="http://feeds.feedburner.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~4/MwgeoWj75AI" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://improving-bpm-systems.blogspot.com/feeds/6871089365894249488/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=4560463190032436692&amp;postID=6871089365894249488" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/6871089365894249488?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/6871089365894249488?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~3/MwgeoWj75AI/enterprise-patterns-make-your-logic.html" title="Enterprise patterns: Make Your Logic Obvious (MYLO)" /><author><name>Alexander SAMARIN</name><uri>https://plus.google.com/112810118258856486156</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-rb1Di6vctuI/AAAAAAAAAAI/AAAAAAAABJQ/gFbMGYq7mqI/s512-c/photo.jpg" /></author><thr:total>0</thr:total><gd:extendedProperty name="commentSource" value="1" /><gd:extendedProperty name="commentModerationMode" value="FILTERED_POSTMOD" /><feedburner:origLink>http://improving-bpm-systems.blogspot.com/2013/04/enterprise-patterns-make-your-logic.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0IFR3g6fCp7ImA9WhBbGEU.&quot;"><id>tag:blogger.com,1999:blog-4560463190032436692.post-4275345076911791089</id><published>2013-04-11T08:30:00.000+02:00</published><updated>2013-05-18T15:58:36.614+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-05-18T15:58:36.614+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="agility" /><category scheme="http://www.blogger.com/atom/ns#" term="BPM" /><title>#bpm for developers: improve #agility of implementations</title><summary type="html">A small presentation for developers about BPM with different tricks to improve the agility and robustness of implementations is available on SlideShare http://fr.slideshare.net/samarin/bpm-for-developers


  

 BPM for developers  from Alexander Samarin 


and its extended version

  

 BPM for developers, extended  from Alexander Samarin 


Thanks,
AS



&lt;img src="http://feeds.feedburner.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~4/bGdwuiM2lxU" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://improving-bpm-systems.blogspot.com/feeds/4275345076911791089/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=4560463190032436692&amp;postID=4275345076911791089" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/4275345076911791089?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/4275345076911791089?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~3/bGdwuiM2lxU/bpm-for-developers-improve-agility-of.html" title="#bpm for developers: improve #agility of implementations" /><author><name>Alexander SAMARIN</name><uri>https://plus.google.com/112810118258856486156</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-rb1Di6vctuI/AAAAAAAAAAI/AAAAAAAABJQ/gFbMGYq7mqI/s512-c/photo.jpg" /></author><thr:total>0</thr:total><gd:extendedProperty name="commentSource" value="1" /><gd:extendedProperty name="commentModerationMode" value="FILTERED_POSTMOD" /><feedburner:origLink>http://improving-bpm-systems.blogspot.com/2013/04/bpm-for-developers-improve-agility-of.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEcERH88fCp7ImA9WhBVEks.&quot;"><id>tag:blogger.com,1999:blog-4560463190032436692.post-2507118429669589616</id><published>2013-04-06T21:24:00.001+02:00</published><updated>2013-04-18T08:20:05.174+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-04-18T08:20:05.174+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="SOA" /><category scheme="http://www.blogger.com/atom/ns#" term="book about BPM SOA EA" /><category scheme="http://www.blogger.com/atom/ns#" term="EA" /><category scheme="http://www.blogger.com/atom/ns#" term="BPM" /><category scheme="http://www.blogger.com/atom/ns#" term="enterprise patterns" /><category scheme="http://www.blogger.com/atom/ns#" term="IT strategy" /><title>Enterprise patterns: Strategy Implementation Chain (SIC)</title><summary type="html">The aim of this post is to synthesize some enterprise patterns recently published in this blog to address the practical enterprise need of “strategy implementation”. The arrangement achieved links different #entarch artefacts into some kind of chain of transformations, with its supervision and enabling:

from the business objectives to a portfolio of projects (or roadmap); 
from the brief initial&lt;img src="http://feeds.feedburner.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~4/C962opauj0o" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://improving-bpm-systems.blogspot.com/feeds/2507118429669589616/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=4560463190032436692&amp;postID=2507118429669589616" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/2507118429669589616?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/2507118429669589616?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~3/C962opauj0o/enterprise-patterns-strategy.html" title="Enterprise patterns: Strategy Implementation Chain (SIC)" /><author><name>Alexander SAMARIN</name><uri>https://plus.google.com/112810118258856486156</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-rb1Di6vctuI/AAAAAAAAAAI/AAAAAAAABJQ/gFbMGYq7mqI/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://4.bp.blogspot.com/-T-pMw_RpEPs/UW7rltst_iI/AAAAAAAAAyk/HBK7xCBpbmg/s72-c/pic1.png" height="72" width="72" /><thr:total>0</thr:total><georss:featurename>Tunisia</georss:featurename><georss:point>36.906977001038335 10.319282361621163</georss:point><georss:box>36.88158750103833 10.278941861621163 36.93236650103834 10.359622861621162</georss:box><gd:extendedProperty name="commentSource" value="1" /><gd:extendedProperty name="commentModerationMode" value="FILTERED_POSTMOD" /><feedburner:origLink>http://improving-bpm-systems.blogspot.com/2013/04/enterprise-patterns-strategy.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CkUDQnk6eip7ImA9WhBaFEU.&quot;"><id>tag:blogger.com,1999:blog-4560463190032436692.post-165560745232667025</id><published>2013-04-06T21:23:00.001+02:00</published><updated>2013-05-25T13:11:13.712+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-05-25T13:11:13.712+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="EA" /><category scheme="http://www.blogger.com/atom/ns#" term="enterprise patterns" /><category scheme="http://www.blogger.com/atom/ns#" term="IT strategy" /><title>Enterprise patterns: Strategy TO Portfolio (STOP)</title><summary type="html">This pattern is based on previous blog posts about linking business priorities and IT portfolio of projects - http://improving-bpm-systems.blogspot.com/search/label/IT%20strategy .

Considering that at present the intended strategy is only a part of the realised strategy, it is necessary to take into account emergent strategy as quick as possible.  Developing a strategy for 3 years and and &lt;img src="http://feeds.feedburner.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~4/DO54kxS1-Lo" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://improving-bpm-systems.blogspot.com/feeds/165560745232667025/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=4560463190032436692&amp;postID=165560745232667025" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/165560745232667025?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/165560745232667025?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~3/DO54kxS1-Lo/enterprise-patterns-strategy-to.html" title="Enterprise patterns: Strategy TO Portfolio (STOP)" /><author><name>Alexander SAMARIN</name><uri>https://plus.google.com/112810118258856486156</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-rb1Di6vctuI/AAAAAAAAAAI/AAAAAAAABJQ/gFbMGYq7mqI/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://3.bp.blogspot.com/-XRmm_25IZQo/UWB0XqWjwMI/AAAAAAAAAyE/kn1xJH66rZs/s72-c/Picture1.png" height="72" width="72" /><thr:total>0</thr:total><gd:extendedProperty name="commentSource" value="1" /><gd:extendedProperty name="commentModerationMode" value="FILTERED_POSTMOD" /><feedburner:origLink>http://improving-bpm-systems.blogspot.com/2013/04/enterprise-patterns-strategy-to.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0UBRn47fyp7ImA9WhBWEUk.&quot;"><id>tag:blogger.com,1999:blog-4560463190032436692.post-3886298125728710627</id><published>2013-04-05T09:00:00.000+02:00</published><updated>2013-04-05T09:00:57.007+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-04-05T09:00:57.007+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="africa" /><category scheme="http://www.blogger.com/atom/ns#" term="EA" /><title>First #entarch works?</title><summary type="html">Mentioning of #entarch work (urbanisme in French) is found on a stone document from Punique Carthage dated at 3rd century (probably) BC.



A description in French is below.











Thanks,

AS






&lt;img src="http://feeds.feedburner.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~4/0nFl-cc-XFE" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://improving-bpm-systems.blogspot.com/feeds/3886298125728710627/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=4560463190032436692&amp;postID=3886298125728710627" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/3886298125728710627?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/3886298125728710627?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~3/0nFl-cc-XFE/first-entarch-works.html" title="First #entarch works?" /><author><name>Alexander SAMARIN</name><uri>https://plus.google.com/112810118258856486156</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-rb1Di6vctuI/AAAAAAAAAAI/AAAAAAAABJQ/gFbMGYq7mqI/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://4.bp.blogspot.com/-PvExzWYwdK0/UV5zjDsU7lI/AAAAAAAAAxU/kNCKmiXWsJQ/s72-c/20110807443.jpg" height="72" width="72" /><thr:total>0</thr:total><georss:featurename>Tunisia</georss:featurename><georss:point>36.780279795871735 10.311355590820312</georss:point><georss:box>36.767561795871735 10.291185590820312 36.792997795871734 10.331525590820313</georss:box><gd:extendedProperty name="commentSource" value="1" /><gd:extendedProperty name="commentModerationMode" value="FILTERED_POSTMOD" /><feedburner:origLink>http://improving-bpm-systems.blogspot.com/2013/04/first-entarch-works.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C08NQn89eCp7ImA9WhBWFks.&quot;"><id>tag:blogger.com,1999:blog-4560463190032436692.post-7949175518465679080</id><published>2013-04-02T11:57:00.001+02:00</published><updated>2013-04-11T08:31:33.160+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-04-11T08:31:33.160+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="e-gov" /><category scheme="http://www.blogger.com/atom/ns#" term="e-government" /><category scheme="http://www.blogger.com/atom/ns#" term="cloud" /><category scheme="http://www.blogger.com/atom/ns#" term="africa" /><category scheme="http://www.blogger.com/atom/ns#" term="BPM" /><category scheme="http://www.blogger.com/atom/ns#" term="security" /><category scheme="http://www.blogger.com/atom/ns#" term="e-governance" /><title>Addressing #security concerns through #BPM</title><summary type="html">A small presentation about potential linkage between security and BPM is available at
http://fr.slideshare.net/samarin/addressing-security-concerns-through-bpm


  

 Addressing security concerns through BPM  from Alexander Samarin 

This linkage is important because BPM should play the main role in the pan-African platform for e-governments and e-governance (see http://&lt;img src="http://feeds.feedburner.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~4/klUlrzaL-ic" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://improving-bpm-systems.blogspot.com/feeds/7949175518465679080/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=4560463190032436692&amp;postID=7949175518465679080" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/7949175518465679080?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/7949175518465679080?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~3/klUlrzaL-ic/addressing-security-concerns-through-bpm.html" title="Addressing #security concerns through #BPM" /><author><name>Alexander SAMARIN</name><uri>https://plus.google.com/112810118258856486156</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-rb1Di6vctuI/AAAAAAAAAAI/AAAAAAAABJQ/gFbMGYq7mqI/s512-c/photo.jpg" /></author><thr:total>0</thr:total><gd:extendedProperty name="commentSource" value="1" /><gd:extendedProperty name="commentModerationMode" value="FILTERED_POSTMOD" /><feedburner:origLink>http://improving-bpm-systems.blogspot.com/2013/04/addressing-security-concerns-through-bpm.html</feedburner:origLink></entry><entry gd:etag="W/&quot;AkQCRnw9fSp7ImA9WhBXFkg.&quot;"><id>tag:blogger.com,1999:blog-4560463190032436692.post-136895203335066127</id><published>2013-03-30T16:46:00.000+01:00</published><updated>2013-03-30T16:46:07.265+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-03-30T16:46:07.265+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="e-gov" /><category scheme="http://www.blogger.com/atom/ns#" term="e-government" /><category scheme="http://www.blogger.com/atom/ns#" term="africa" /><category scheme="http://www.blogger.com/atom/ns#" term="e-governance" /><title>Pan-African platform for e-governments and e-governance to speed-up Africa’s transformation</title><summary type="html">
Executive summary
It is not a secret that Africa must redouble efforts to build efficient, resilient and capable states. The modern way to improve the activities of public sector organisations is to use the Information and Communication Technologies (ICTs). There are many world-wide examples which allow saying that the sooner Africa will have governments which are fully tech-enabled with a &lt;img src="http://feeds.feedburner.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~4/I19-nF6HPYg" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://improving-bpm-systems.blogspot.com/feeds/136895203335066127/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=4560463190032436692&amp;postID=136895203335066127" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/136895203335066127?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/136895203335066127?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~3/I19-nF6HPYg/pan-african-platform-for-e-governments.html" title="Pan-African platform for e-governments and e-governance to speed-up Africa’s transformation" /><author><name>Alexander SAMARIN</name><uri>https://plus.google.com/112810118258856486156</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-rb1Di6vctuI/AAAAAAAAAAI/AAAAAAAABJQ/gFbMGYq7mqI/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://2.bp.blogspot.com/-3TjERlv2eMc/UVb992z0uaI/AAAAAAAAAwk/bzDAOSsYcQo/s72-c/image001.jpg" height="72" width="72" /><thr:total>1</thr:total><gd:extendedProperty name="commentSource" value="1" /><gd:extendedProperty name="commentModerationMode" value="FILTERED_POSTMOD" /><feedburner:origLink>http://improving-bpm-systems.blogspot.com/2013/03/pan-african-platform-for-e-governments.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CUMGSHc8cSp7ImA9WhFSEUQ.&quot;"><id>tag:blogger.com,1999:blog-4560463190032436692.post-3452600542580325044</id><published>2013-03-12T13:51:00.001+01:00</published><updated>2013-06-14T09:03:49.979+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-06-14T09:03:49.979+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="terminology" /><category scheme="http://www.blogger.com/atom/ns#" term="BA" /><title>#bizarch artefacts definition; again</title><summary type="html">This post is written for the LinkedIn discussion "Whats the defference between, a Business Capability, a Business Function, a Business Process and a Service?"
In this post, I collected (and refined) several #bizarch definitions from the posts about #bizarch.

activity, noun
elementary or indivisible unit of work

function, noun
abstract and self-contained grouping of activities that collectively &lt;img src="http://feeds.feedburner.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~4/ZAACl2va8ig" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://improving-bpm-systems.blogspot.com/feeds/3452600542580325044/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=4560463190032436692&amp;postID=3452600542580325044" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/3452600542580325044?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/3452600542580325044?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~3/ZAACl2va8ig/bizarch-artefacts-definition-again.html" title="#bizarch artefacts definition; again" /><author><name>Alexander SAMARIN</name><uri>https://plus.google.com/112810118258856486156</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-rb1Di6vctuI/AAAAAAAAAAI/AAAAAAAABJQ/gFbMGYq7mqI/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://4.bp.blogspot.com/-KxC6qnwmZ9M/UT8f-1R9WVI/AAAAAAAAAwQ/mLN0XFkAFWY/s72-c/q.png" height="72" width="72" /><thr:total>0</thr:total><gd:extendedProperty name="commentSource" value="1" /><gd:extendedProperty name="commentModerationMode" value="FILTERED_POSTMOD" /><feedburner:origLink>http://improving-bpm-systems.blogspot.com/2013/03/bizarch-artefacts-definition-again.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CkADRXg-eip7ImA9WhBRE0w.&quot;"><id>tag:blogger.com,1999:blog-4560463190032436692.post-6881395485842776686</id><published>2013-03-03T12:39:00.001+01:00</published><updated>2013-03-03T12:39:34.652+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-03-03T12:39:34.652+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="EA" /><title>Architects are responsible for HOW thus capability of WHAT</title><summary type="html">Many recent discussions were talking about WHY, WHAT, and HOW as outputs of architectural work.   I already blogged about dependencies / linking between them (see http://improving-bpm-systems.blogspot.com/2011/02/explaining-ea-business-architecture_19.html ).

In this post, I would like to outline who is responsible for WHY, WHAT and HOW. But, at first, let go back to basics and define "architect&lt;img src="http://feeds.feedburner.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~4/pZQ-8D99C-A" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://improving-bpm-systems.blogspot.com/feeds/6881395485842776686/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=4560463190032436692&amp;postID=6881395485842776686" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/6881395485842776686?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/6881395485842776686?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~3/pZQ-8D99C-A/architects-are-responsible-for-how-thus.html" title="Architects are responsible for HOW thus capability of WHAT" /><author><name>Alexander SAMARIN</name><uri>https://plus.google.com/112810118258856486156</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-rb1Di6vctuI/AAAAAAAAAAI/AAAAAAAABJQ/gFbMGYq7mqI/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://1.bp.blogspot.com/-drkVWrVpR4w/UTMeJHPQSFI/AAAAAAAAAwA/Ou97n5neWh4/s72-c/Picture2.png" height="72" width="72" /><thr:total>2</thr:total><gd:extendedProperty name="commentSource" value="1" /><gd:extendedProperty name="commentModerationMode" value="FILTERED_POSTMOD" /><feedburner:origLink>http://improving-bpm-systems.blogspot.com/2013/03/architects-are-responsible-for-how-thus.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A08HRnYzeCp7ImA9WhBbFUQ.&quot;"><id>tag:blogger.com,1999:blog-4560463190032436692.post-4576737501606851256</id><published>2013-03-02T19:27:00.001+01:00</published><updated>2013-05-15T08:37:17.880+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-05-15T08:37:17.880+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="EA" /><title>Result-Based Logical Framework</title><summary type="html">Idea of results chain... Outputs -&amp;gt; Outcome -&amp;gt; Impact.

















Thanks,

AS

&lt;img src="http://feeds.feedburner.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~4/Yf-tNdek7e0" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://improving-bpm-systems.blogspot.com/feeds/4576737501606851256/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=4560463190032436692&amp;postID=4576737501606851256" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/4576737501606851256?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/4576737501606851256?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~3/Yf-tNdek7e0/result-based-logical-framework.html" title="Result-Based Logical Framework" /><author><name>Alexander SAMARIN</name><uri>https://plus.google.com/112810118258856486156</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-rb1Di6vctuI/AAAAAAAAAAI/AAAAAAAABJQ/gFbMGYq7mqI/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://3.bp.blogspot.com/-W4yDQ7cK5Nw/US38UdB-fYI/AAAAAAAAAvw/dps-XoylEaA/s72-c/logframe+2013-02-27+13-28-55.png" height="72" width="72" /><thr:total>0</thr:total><gd:extendedProperty name="commentSource" value="1" /><gd:extendedProperty name="commentModerationMode" value="FILTERED_POSTMOD" /><feedburner:origLink>http://improving-bpm-systems.blogspot.com/2013/03/result-based-logical-framework.html</feedburner:origLink></entry><entry gd:etag="W/&quot;Ck8GR3Y5eyp7ImA9WhFTGUU.&quot;"><id>tag:blogger.com,1999:blog-4560463190032436692.post-3811746651391363798</id><published>2013-02-27T13:05:00.001+01:00</published><updated>2013-06-11T22:00:26.823+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-06-11T22:00:26.823+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="BPM" /><category scheme="http://www.blogger.com/atom/ns#" term="PEAS" /><category scheme="http://www.blogger.com/atom/ns#" term="enterprise patterns" /><title>Enterprise patterns: PEAS - example and technique</title><summary type="html">This post is an example of introduction a PEAS-architected platform (see http://improving-bpm-systems.blogspot.com/2011/04/enterprise-patterns-peas.html). IN this example, BPM was used as a technique to reveal  the platform.

The situation:
An organisation (which printed 30 mil pages per year) had about 40 publishing tools. The attempt to replace them by a common tool has failed after 2 years of &lt;img src="http://feeds.feedburner.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~4/A-tojCKsrYQ" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://improving-bpm-systems.blogspot.com/feeds/3811746651391363798/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=4560463190032436692&amp;postID=3811746651391363798" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/3811746651391363798?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/3811746651391363798?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~3/A-tojCKsrYQ/enterprise-patterns-peas-example-and.html" title="Enterprise patterns: PEAS - example and technique" /><author><name>Alexander SAMARIN</name><uri>https://plus.google.com/112810118258856486156</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-rb1Di6vctuI/AAAAAAAAAAI/AAAAAAAABJQ/gFbMGYq7mqI/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://4.bp.blogspot.com/-2BycOiHLH6w/US2wH5-WlzI/AAAAAAAAAvU/pzoeVl-jYCU/s72-c/Picture1.png" height="72" width="72" /><thr:total>0</thr:total><gd:extendedProperty name="commentSource" value="1" /><gd:extendedProperty name="commentModerationMode" value="FILTERED_POSTMOD" /><feedburner:origLink>http://improving-bpm-systems.blogspot.com/2013/02/enterprise-patterns-peas-example-and.html</feedburner:origLink></entry><entry gd:etag="W/&quot;Dk4ARXkyeCp7ImA9WhBSGUk.&quot;"><id>tag:blogger.com,1999:blog-4560463190032436692.post-3542375433487053282</id><published>2013-02-27T07:02:00.000+01:00</published><updated>2013-02-27T07:02:24.790+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-02-27T07:02:24.790+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="EA" /><category scheme="http://www.blogger.com/atom/ns#" term="BPM" /><title>Towards "paperless" or "digital" or "less paper" way of working</title><summary type="html">Just a few slides from the EA + BPM + SOA + ECM point of view..

































Thanks,
AS&lt;img src="http://feeds.feedburner.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~4/IaMz9rwPHP4" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://improving-bpm-systems.blogspot.com/feeds/3542375433487053282/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=4560463190032436692&amp;postID=3542375433487053282" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/3542375433487053282?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/3542375433487053282?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~3/IaMz9rwPHP4/towards-paperless-or-digital-or-less.html" title="Towards &quot;paperless&quot; or &quot;digital&quot; or &quot;less paper&quot; way of working" /><author><name>Alexander SAMARIN</name><uri>https://plus.google.com/112810118258856486156</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-rb1Di6vctuI/AAAAAAAAAAI/AAAAAAAABJQ/gFbMGYq7mqI/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://3.bp.blogspot.com/-qqPiqitPAqw/USysY5vXE5I/AAAAAAAAAt8/gKDLznli_Us/s72-c/PLO+1+2013-02-26+13-31-23.png" height="72" width="72" /><thr:total>0</thr:total><gd:extendedProperty name="commentSource" value="1" /><gd:extendedProperty name="commentModerationMode" value="FILTERED_POSTMOD" /><feedburner:origLink>http://improving-bpm-systems.blogspot.com/2013/02/towards-paperless-or-digital-or-less.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DUYFQX85eSp7ImA9WhBSF0Q.&quot;"><id>tag:blogger.com,1999:blog-4560463190032436692.post-2895576075881908923</id><published>2013-02-25T13:57:00.001+01:00</published><updated>2013-02-25T13:58:30.121+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-02-25T13:58:30.121+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="BPM" /><title>How #BPM can help to a broken banking transaction</title><summary type="html">Yesterday, I made (via the "ebanking" interface) a transfer from my USD account (or sub-account) to my CHF account (or sub-account). Such a transfer is an internal transaction and it is executed immediately during normal working days.

As yesterday was Sunday then this transaction was postponed to Monday. At 7:30 AM on Monday I noticed that my USD account was debited at 4:14 AM, but my CHF &lt;img src="http://feeds.feedburner.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~4/AWFFqKeEhaM" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://improving-bpm-systems.blogspot.com/feeds/2895576075881908923/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=4560463190032436692&amp;postID=2895576075881908923" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/2895576075881908923?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/2895576075881908923?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~3/AWFFqKeEhaM/how-bpm-can-help-to-broken-banking.html" title="How #BPM can help to a broken banking transaction" /><author><name>Alexander SAMARIN</name><uri>https://plus.google.com/112810118258856486156</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-rb1Di6vctuI/AAAAAAAAAAI/AAAAAAAABJQ/gFbMGYq7mqI/s512-c/photo.jpg" /></author><thr:total>0</thr:total><gd:extendedProperty name="commentSource" value="1" /><gd:extendedProperty name="commentModerationMode" value="FILTERED_POSTMOD" /><feedburner:origLink>http://improving-bpm-systems.blogspot.com/2013/02/how-bpm-can-help-to-broken-banking.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A0QCQ3Y9cSp7ImA9WhBRE00.&quot;"><id>tag:blogger.com,1999:blog-4560463190032436692.post-6086713258830277530</id><published>2013-02-24T16:18:00.003+01:00</published><updated>2013-03-03T12:16:02.869+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-03-03T12:16:02.869+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="systems thinking" /><category scheme="http://www.blogger.com/atom/ns#" term="IT strategy" /><title>Linking business strategy and IT strategy</title><summary type="html">This post is a continuation of "Writing IT strategy - From business priorities to the planning of IT actions".

The main picture from the previous post is extended to explicitly link move concepts (business startegic objectives, business initiatives, business capabilities, IT capabilities (generic supply), IT tools (specific supply) and IT programmes.




This is a possible way to "...setting out&lt;img src="http://feeds.feedburner.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~4/u04zQ3gZnoA" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://improving-bpm-systems.blogspot.com/feeds/6086713258830277530/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=4560463190032436692&amp;postID=6086713258830277530" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/6086713258830277530?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/6086713258830277530?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~3/u04zQ3gZnoA/linking-business-strategy-and-it.html" title="Linking business strategy and IT strategy" /><author><name>Alexander SAMARIN</name><uri>https://plus.google.com/112810118258856486156</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-rb1Di6vctuI/AAAAAAAAAAI/AAAAAAAABJQ/gFbMGYq7mqI/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://1.bp.blogspot.com/-x7VmfTet6HU/USon0XrX8kI/AAAAAAAAAqo/XDOK7mnESjY/s72-c/a.png" height="72" width="72" /><thr:total>0</thr:total><gd:extendedProperty name="commentSource" value="1" /><gd:extendedProperty name="commentModerationMode" value="FILTERED_POSTMOD" /><feedburner:origLink>http://improving-bpm-systems.blogspot.com/2013/02/linking-business-strategy-and-it.html</feedburner:origLink></entry><entry gd:etag="W/&quot;Ck8CR3s4fip7ImA9WhFTGUU.&quot;"><id>tag:blogger.com,1999:blog-4560463190032436692.post-3123941248668109191</id><published>2013-02-24T15:37:00.000+01:00</published><updated>2013-06-11T22:01:06.536+02:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-06-11T22:01:06.536+02:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="agility" /><category scheme="http://www.blogger.com/atom/ns#" term="PEAS" /><category scheme="http://www.blogger.com/atom/ns#" term="enterprise patterns" /><title>Quick delivery of solutions via a PEAS-architected platform - mini-projects</title><summary type="html">This is a continuation of the post Quick delivery of solutions via a PEAS-architected platform" to describe functioning of mini-projects.


Roles within mini-projects (are taken from the DAD book)
A stakeholder is someone who is materially impacted by the outcome of the solution. In this regard, the stakeholder is clearly more than an end user.

The team lead (TL) is a servant-leader to the team,&lt;img src="http://feeds.feedburner.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~4/PFc2Ng87Cj8" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://improving-bpm-systems.blogspot.com/feeds/3123941248668109191/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=4560463190032436692&amp;postID=3123941248668109191" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/3123941248668109191?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/3123941248668109191?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~3/PFc2Ng87Cj8/quick-delivery-of-solutions-via-peas.html" title="Quick delivery of solutions via a PEAS-architected platform - mini-projects" /><author><name>Alexander SAMARIN</name><uri>https://plus.google.com/112810118258856486156</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-rb1Di6vctuI/AAAAAAAAAAI/AAAAAAAABJQ/gFbMGYq7mqI/s512-c/photo.jpg" /></author><thr:total>0</thr:total><gd:extendedProperty name="commentSource" value="1" /><gd:extendedProperty name="commentModerationMode" value="FILTERED_POSTMOD" /><feedburner:origLink>http://improving-bpm-systems.blogspot.com/2013/02/quick-delivery-of-solutions-via-peas.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CEQBQHcyeCp7ImA9WhBSFE4.&quot;"><id>tag:blogger.com,1999:blog-4560463190032436692.post-2865328951364714717</id><published>2013-02-13T10:37:00.001+01:00</published><updated>2013-02-21T08:39:11.990+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-02-21T08:39:11.990+01:00</app:edited><category scheme="http://www.blogger.com/atom/ns#" term="e-gov" /><category scheme="http://www.blogger.com/atom/ns#" term="EA" /><category scheme="http://www.blogger.com/atom/ns#" term="enterprise architecture" /><title>#entarch was mentioned in Davos at WEF</title><summary type="html">
From  http://www3.weforum.org/docs/EU11/WEF_EU11_FutureofGovernment_Report.pdf

An Enterprise Architectural Approach. e-Government may be thought of as a complex socio-economic and
human-machine system, which has begun to be explored and developed in recent years with the use of the Enterprise Architecture (EA) methodology. This approach encompasses a generalized representation of the subject &lt;img src="http://feeds.feedburner.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~4/mn3miGFMSHo" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://improving-bpm-systems.blogspot.com/feeds/2865328951364714717/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=4560463190032436692&amp;postID=2865328951364714717" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/2865328951364714717?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/2865328951364714717?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~3/mn3miGFMSHo/entarch-was-mentioned-in-davos-at-wef.html" title="#entarch was mentioned in Davos at WEF" /><author><name>Alexander SAMARIN</name><uri>https://plus.google.com/112810118258856486156</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-rb1Di6vctuI/AAAAAAAAAAI/AAAAAAAABJQ/gFbMGYq7mqI/s512-c/photo.jpg" /></author><thr:total>0</thr:total><gd:extendedProperty name="commentSource" value="1" /><gd:extendedProperty name="commentModerationMode" value="FILTERED_POSTMOD" /><feedburner:origLink>http://improving-bpm-systems.blogspot.com/2013/02/entarch-was-mentioned-in-davos-at-wef.html</feedburner:origLink></entry><entry gd:etag="W/&quot;AkUGQXY8fCp7ImA9WhBTF0k.&quot;"><id>tag:blogger.com,1999:blog-4560463190032436692.post-83546219094927528</id><published>2013-02-13T10:37:00.000+01:00</published><updated>2013-02-13T10:37:00.874+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2013-02-13T10:37:00.874+01:00</app:edited><title>You have one of the top 1% most viewed LinkedIn profiles for 2012</title><summary type="html">



Thanks,
AS&lt;img src="http://feeds.feedburner.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~4/mIjVob311NI" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://improving-bpm-systems.blogspot.com/feeds/83546219094927528/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=4560463190032436692&amp;postID=83546219094927528" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/83546219094927528?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/83546219094927528?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~3/mIjVob311NI/you-have-one-of-top-1-most-viewed.html" title="You have one of the top 1% most viewed LinkedIn profiles for 2012" /><author><name>Alexander SAMARIN</name><uri>https://plus.google.com/112810118258856486156</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-rb1Di6vctuI/AAAAAAAAAAI/AAAAAAAABJQ/gFbMGYq7mqI/s512-c/photo.jpg" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://1.bp.blogspot.com/-YDRfE1cVPio/URpE-NHFylI/AAAAAAAAAqQ/uihjiof7u2Y/s72-c/2013-02-12+14-32-11.png" height="72" width="72" /><thr:total>0</thr:total><gd:extendedProperty name="commentSource" value="1" /><gd:extendedProperty name="commentModerationMode" value="FILTERED_POSTMOD" /><feedburner:origLink>http://improving-bpm-systems.blogspot.com/2013/02/you-have-one-of-top-1-most-viewed.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A0ACSHY-fip7ImA9WhNWE04.&quot;"><id>tag:blogger.com,1999:blog-4560463190032436692.post-6834955399557935445</id><published>2012-12-12T20:16:00.000+01:00</published><updated>2012-12-12T20:16:09.856+01:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2012-12-12T20:16:09.856+01:00</app:edited><title>This blog is in the list of "BPM Blogs worth reading 2012"</title><summary type="html">Again in the list of "BPM Blogs worth reading 2012" from Alberto Manuel.

See http://ultrabpm.wordpress.com/2012/12/12/bpm-blogs-worth-reading-2012/

Thanks,
AS
&lt;img src="http://feeds.feedburner.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~4/mt8NK_OSVZw" height="1" width="1"/&gt;</summary><link rel="replies" type="application/atom+xml" href="http://improving-bpm-systems.blogspot.com/feeds/6834955399557935445/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.blogger.com/comment.g?blogID=4560463190032436692&amp;postID=6834955399557935445" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/6834955399557935445?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/4560463190032436692/posts/default/6834955399557935445?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/ImprovingEnterpriseBusinessProcessManagementSystems/~3/mt8NK_OSVZw/this-blog-is-in-list-of-bpm-blogs-worth.html" title="This blog is in the list of &quot;BPM Blogs worth reading 2012&quot;" /><author><name>Alexander SAMARIN</name><uri>https://plus.google.com/112810118258856486156</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="32" height="32" src="//lh5.googleusercontent.com/-rb1Di6vctuI/AAAAAAAAAAI/AAAAAAAABJQ/gFbMGYq7mqI/s512-c/photo.jpg" /></author><thr:total>0</thr:total><gd:extendedProperty name="commentSource" value="1" /><gd:extendedProperty name="commentModerationMode" value="FILTERED_POSTMOD" /><feedburner:origLink>http://improving-bpm-systems.blogspot.com/2012/12/this-blog-is-in-list-of-bpm-blogs-worth.html</feedburner:origLink></entry></feed>
