<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic BPM estimation technique in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/bpm-estimation-technique/m-p/201978#M155108</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I am new to this BPM space. I have worked on many projects that are developed conventionally, for which I have always used techniques like UCP, FPA or WBS to calculate the efforts required to develop the projects. However, since I am planning to propose BPMS tools like Activiti to one of my Customers I am looking for information on how to estimate efforts for BPM projects. I am pretty sure there exists one where in estimate accounts for number and complexity of the processes, services, rules, etc. I am also sure that the development time will be lesser than the conventional methods. I am just not able to find any reliable resource. Can anyone help? &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks.&lt;/SPAN&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 26 Aug 2014 13:17:35 GMT</pubDate>
    <dc:creator>ashishshinde</dc:creator>
    <dc:date>2014-08-26T13:17:35Z</dc:date>
    <item>
      <title>BPM estimation technique</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/bpm-estimation-technique/m-p/201978#M155108</link>
      <description>HiI am new to this BPM space. I have worked on many projects that are developed conventionally, for which I have always used techniques like UCP, FPA or WBS to calculate the efforts required to develop the projects. However, since I am planning to propose BPMS tools like Activiti to one of my Custom</description>
      <pubDate>Tue, 26 Aug 2014 13:17:35 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/bpm-estimation-technique/m-p/201978#M155108</guid>
      <dc:creator>ashishshinde</dc:creator>
      <dc:date>2014-08-26T13:17:35Z</dc:date>
    </item>
    <item>
      <title>Re: BPM estimation technique</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/bpm-estimation-technique/m-p/201979#M155109</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;My humble opinion is that all estimation techniques are bad &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;So sorry can't really help you beyond pointing out that most of Activiti is Java code and hence you should estimate the work as regular Java, back-end work&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 30 Aug 2014 17:52:49 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/bpm-estimation-technique/m-p/201979#M155109</guid>
      <dc:creator>jbarrez</dc:creator>
      <dc:date>2014-08-30T17:52:49Z</dc:date>
    </item>
    <item>
      <title>Re: BPM estimation technique</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/bpm-estimation-technique/m-p/201980#M155110</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Estimation based on amount of process steps does not work. From my point of view integration consumes major part of planned/unplanned effort.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Martin&lt;/SPAN&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Sep 2014 05:55:04 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/bpm-estimation-technique/m-p/201980#M155110</guid>
      <dc:creator>martin_grofcik</dc:creator>
      <dc:date>2014-09-01T05:55:04Z</dc:date>
    </item>
  </channel>
</rss>

