<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://community.appian.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>What is the best practice of Appian project from gathering requirement to delivery Appian process/es?</title><link>https://community.appian.com/discussions/f/best-practices/2699/what-is-the-best-practice-of-appian-project-from-gathering-requirement-to-delivery-appian-process-es</link><description>Hi, What is the best practice of Appian project from gathering requirement to delivery Appian process/es Thanks,... 
 OriginalPostID-110096 
 OriginalPostID-110096</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: What is the best practice of Appian project from gathering requirement to delivery Appian process/es?</title><link>https://community.appian.com/thread/9389?ContentTypeID=1</link><pubDate>Sat, 17 May 2014 22:56:16 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:4c950770-17fb-4cdc-a8b4-8aae2a9df4fe</guid><dc:creator>padmanabhanv</dc:creator><description>It is a BPM best practice to start with modeling the AS-IS process model, check its conformity with business and then move on to modeling the TO-BE process, socialize it with business and then move ahead to granular details. &lt;br /&gt;So at the end of the modeling exercise you should have an L1(level 1 - high level) and multiple L2&amp;#39;s depicting all identified sub processes too. &lt;br /&gt;Collecting reporting requirements upfront is important since that plays a major part in designing your cdt&amp;#39;s and persistence strategy.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: What is the best practice of Appian project from gathering requirement to delivery Appian process/es?</title><link>https://community.appian.com/thread/9387?ContentTypeID=1</link><pubDate>Sat, 17 May 2014 22:15:37 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:7df734a6-9cba-43bb-8969-0756041b711c</guid><dc:creator>amerm190</dc:creator><description>Yeah I checked, but if there another Appian standard&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: What is the best practice of Appian project from gathering requirement to delivery Appian process/es?</title><link>https://community.appian.com/thread/9384?ContentTypeID=1</link><pubDate>Sat, 17 May 2014 21:32:14 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:43012c75-e8d9-4828-bfd8-47d8434ff0e2</guid><dc:creator>Stefan Helzle</dc:creator><description>Did you check the Appian STAR methodology? That should give you a good start.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>