<?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/"><channel><title>Reuse Promotion</title><link>https://community.appian.com/success/w/guide/2971/reuse-promotion</link><description /><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>Reuse Promotion</title><link>https://community.appian.com/success/w/guide/2971/reuse-promotion</link><pubDate>Tue, 23 Apr 2024 13:11:01 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:2ca2905e-dd89-4200-a7fd-112ee18d4fe5</guid><dc:creator>Appian Max Team</dc:creator><comments>https://community.appian.com/success/w/guide/2971/reuse-promotion#comments</comments><description>Current Revision posted to Guide by Appian Max Team on 4/23/2024 1:11:01 PM&lt;br /&gt;
&lt;div style="margin:8px 16% 8px 8%;"&gt;
&lt;h2 id="skills_covered"&gt;Skills Covered&lt;/h2&gt;
&lt;p style="font-size:115%;"&gt;&lt;span style="font-weight:400;"&gt;Reusing Appian components and interfaces ensures a consistent look and feel to your applications, while also promoting efficient development practices.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p style="font-size:115%;"&gt;&lt;span style="font-weight:400;"&gt;Skills Checklist:&lt;/span&gt;&lt;/p&gt;
&lt;ul style="font-size:115%;"&gt;
&lt;li style="font-weight:400;"&gt;Identify benefits to reusing Appian components and interfaces in development.&lt;/li&gt;
&lt;li style="font-weight:400;"&gt;&lt;span style="font-weight:400;"&gt;List three&amp;nbsp;frequently reused Appian&amp;nbsp;components.&lt;/span&gt;&lt;/li&gt;
&lt;li style="font-weight:400;"&gt;Identify strategies to ensure proper handling of reusable components.&amp;nbsp;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="platform_consistency"&gt;Platform Consistency&lt;/h2&gt;
&lt;p style="font-size:115%;"&gt;&lt;span style="font-weight:400;"&gt;Ensuring applications built on the same platform have a consistent look, feel and flow is a key strategy for improving user experience and accelerating adoption. Enabling the&lt;a href="https://docs.appian.com/suite/help/20.3/using_interfaces_in_appian.html?utm_source=INTERFACELINK&amp;amp;utm_medium=Community&amp;amp;utm_campaign=APM"&gt; reuse of Appian components and interfaces&lt;/a&gt; is one way to achieve this consistency. In addition, application object reuse enables enterprise-wide programs to more efficiently deliver solutions. Reused objects in the form of complex process models, web APIs, business rules, and integrations aid the implementation teams from having to &amp;lsquo;reinvent the wheel&amp;rsquo; every time they start a new application. While maintaining reusable code does require developer attention, that maintenance actually serves as another advantage, as enhancements and bug fixes need only be implemented in one place.&lt;/span&gt;&lt;/p&gt;
&lt;h2 id="plan_for_reuse"&gt;Plan for Reuse&lt;/h2&gt;
&lt;p style="font-size:115%;"&gt;&lt;span style="font-weight:400;"&gt;Appian recommends that project teams &amp;lsquo;plan&amp;rsquo; for reuse during project kickoff &amp;ndash; sprint 0 &amp;ndash; and on an ongoing basis during the planning sessions &amp;ndash; sprint planning and design sessions. The degree to which functionalities can be reused are only limited to the amount of thought put into defining which areas should be reused in order to accelerate delivery. Teams should discuss shared interfaces early to determine which interfaces will be shared and developers can build for reuse. During the planning sessions, Appian recommends identifying business objects that may be reused within the same project/application as well as by other projects/applications within Appian as utilities and outside of Appian as web APIs.&lt;/span&gt;&lt;/p&gt;
&lt;p style="font-size:115%;"&gt;&lt;span style="font-weight:400;"&gt;Utility functions and process models are common candidates for the reusable objects; for example rules and process models that handle text/data manipulation, document generation, audit history logging, etc. Appian allows&lt;a href="/w/the-appian-playbook/2176/frequently-reused-appian-components?utm_source=FUCOMPLINK&amp;amp;utm_medium=Community&amp;amp;utm_campaign=APM"&gt; for a high degree of re-usability &lt;/a&gt;from user interfaces, integrations, processes, and business rules.&lt;/span&gt;&lt;/p&gt;
&lt;p style="font-size:115%;"&gt;&lt;span style="font-weight:400;"&gt;To foster proper change management and enhanced transparency around the reusable components built on Appian, Appian recommends naming conventions which must be clearly documented and followed by all teams. Testing and impact analysis processes are also necessary to ensure that modifications to reusable components doesn&amp;rsquo;t break other applications.&lt;/span&gt;&lt;/p&gt;
&lt;h3&gt;&lt;span class="emoticon" data-url="https://community.appian.com/cfs-file/__key/system/emoji/1f4a1.svg" title="Bulb"&gt;&amp;#x1f4a1;&lt;/span&gt;Practitioner Tip: Don&amp;rsquo;t Overlook Potential Change Management Risk&lt;/h3&gt;
&lt;p style="font-size:115%;"&gt;&lt;span style="font-weight:400;"&gt;Change Management is critical for program success. However, it is often overlooked and left until the application is ready to launch. It is important to define the change early with business and technical stakeholders, identify change agents, create the plan, pilot it and rollout to the end users. There are several factors to keep in mind here including technology transition, end user training, support needs, monitoring adoption, managing feedback from users and planning future changes.&lt;/span&gt;&lt;/p&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Delivery, Architecture&lt;/div&gt;
</description></item><item><title>Reuse Promotion</title><link>https://community.appian.com/success/w/guide/2971/reuse-promotion/revision/4</link><pubDate>Thu, 18 Apr 2024 15:36:24 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:2ca2905e-dd89-4200-a7fd-112ee18d4fe5</guid><dc:creator>Appian Max Team</dc:creator><comments>https://community.appian.com/success/w/guide/2971/reuse-promotion#comments</comments><description>Revision 4 posted to Guide by Appian Max Team on 4/18/2024 3:36:24 PM&lt;br /&gt;
&lt;div style="margin:8px 16% 8px 8%;"&gt;
&lt;h2 id="skills_covered"&gt;Skills Covered&lt;/h2&gt;
&lt;p style="font-size:115%;"&gt;&lt;span style="font-weight:400;"&gt;Reusing Appian components and interfaces ensures a consistent look and feel to your applications, while also promoting efficient development practices.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p style="font-size:115%;"&gt;&lt;span style="font-weight:400;"&gt;Skills Checklist:&lt;/span&gt;&lt;/p&gt;
&lt;ul style="font-size:115%;"&gt;
&lt;li style="font-weight:400;"&gt;Identify benefits to reusing Appian components and interfaces in development.&lt;/li&gt;
&lt;li style="font-weight:400;"&gt;&lt;span style="font-weight:400;"&gt;List three&amp;nbsp;frequently reused Appian&amp;nbsp;components.&lt;/span&gt;&lt;/li&gt;
&lt;li style="font-weight:400;"&gt;Identify strategies to ensure proper handling of reusable components.&amp;nbsp;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="platform_consistency"&gt;Platform Consistency&lt;/h2&gt;
&lt;p style="font-size:115%;"&gt;&lt;span style="font-weight:400;"&gt;Ensuring applications built on the same platform have a consistent look, feel and flow is a key strategy for improving user experience and accelerating adoption. Enabling the&lt;a href="https://docs.appian.com/suite/help/20.3/using_interfaces_in_appian.html?utm_source=INTERFACELINK&amp;amp;utm_medium=Community&amp;amp;utm_campaign=APM"&gt; reuse of Appian components and interfaces&lt;/a&gt; is one way to achieve this consistency. In addition, application object reuse enables enterprise-wide programs to more efficiently deliver solutions. Reused objects in the form of complex process models, web APIs, business rules, and integrations aid the implementation teams from having to &amp;lsquo;reinvent the wheel&amp;rsquo; every time they start a new application. While maintaining reusable code does require developer attention, that maintenance actually serves as another advantage, as enhancements and bug fixes need only be implemented in one place.&lt;/span&gt;&lt;/p&gt;
&lt;h2 id="plan_for_reuse"&gt;Plan for Reuse&lt;/h2&gt;
&lt;p style="font-size:115%;"&gt;&lt;span style="font-weight:400;"&gt;Appian recommends that project teams &amp;lsquo;plan&amp;rsquo; for reuse during project kickoff &amp;ndash; sprint 0 &amp;ndash; and on an ongoing basis during the planning sessions &amp;ndash; sprint planning and design sessions. The degree to which functionalities can be reused are only limited to the amount of thought put into defining which areas should be reused in order to accelerate delivery. Teams should discuss shared interfaces early to determine which interfaces will be shared and developers can build for reuse. During the planning sessions, Appian recommends identifying business objects that may be reused within the same project/application as well as by other projects/applications within Appian as utilities and outside of Appian as web APIs.&lt;/span&gt;&lt;/p&gt;
&lt;p style="font-size:115%;"&gt;&lt;span style="font-weight:400;"&gt;Utility functions and process models are common candidates for the reusable objects; for example rules and process models that handle text/data manipulation, document generation, audit history logging, etc. Appian allows&lt;a href="/w/the-appian-playbook/2176/frequently-reused-appian-components?utm_source=FUCOMPLINK&amp;amp;utm_medium=Community&amp;amp;utm_campaign=APM"&gt; for a high degree of re-usability &lt;/a&gt;from user interfaces, integrations, processes, and business rules.&lt;/span&gt;&lt;/p&gt;
&lt;p style="font-size:115%;"&gt;&lt;span style="font-weight:400;"&gt;To foster proper change management and enhanced transparency around the reusable components built on Appian, Appian recommends naming conventions which must be clearly documented and followed by all teams. Testing and impact analysis processes are also necessary to ensure that modifications to reusable components doesn&amp;rsquo;t break other applications.&lt;/span&gt;&lt;/p&gt;
&lt;h3&gt;&lt;span class="emoticon" data-url="https://community.appian.com/cfs-file/__key/system/emoji/1f4a1.svg" title="Bulb"&gt;&amp;#x1f4a1;&lt;/span&gt;Practitioner Tip: Don&amp;rsquo;t Overlook Potential Change Management Risk&lt;/h3&gt;
&lt;p style="font-size:115%;"&gt;&lt;span style="font-weight:400;"&gt;Change Management is critical for program success. However, it is often overlooked and left until the application is ready to launch. It is important to define the change early with business and technical stakeholders, identify change agents, create the plan, pilot it and rollout to the end users. There are several factors to keep in mind here including technology transition, end user training, support needs, monitoring adoption, managing feedback from users and planning future changes.&lt;/span&gt;&lt;/p&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Delivery, Architecture&lt;/div&gt;
</description></item><item><title>Reuse Promotion</title><link>https://community.appian.com/success/w/guide/2971/reuse-promotion/revision/3</link><pubDate>Tue, 18 Apr 2023 19:24:08 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:2ca2905e-dd89-4200-a7fd-112ee18d4fe5</guid><dc:creator>joel.larin</dc:creator><comments>https://community.appian.com/success/w/guide/2971/reuse-promotion#comments</comments><description>Revision 3 posted to Guide by joel.larin on 4/18/2023 7:24:08 PM&lt;br /&gt;
&lt;div style="margin:8px 16% 8px 8%;"&gt;
&lt;h2 id="skills_covered"&gt;Skills Covered&lt;/h2&gt;
&lt;p style="font-size:115%;"&gt;&lt;span style="font-weight:400;"&gt;Reusing Appian components and interfaces ensures a consistent look and feel to your applications, while also promoting efficient development practices.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p style="font-size:115%;"&gt;&lt;span style="font-weight:400;"&gt;Skills Checklist:&lt;/span&gt;&lt;/p&gt;
&lt;ul style="font-size:115%;"&gt;
&lt;li style="font-weight:400;"&gt;Identify benefits to reusing Appian components and interfaces in development.&lt;/li&gt;
&lt;li style="font-weight:400;"&gt;&lt;span style="font-weight:400;"&gt;List three&amp;nbsp;frequently reused Appian&amp;nbsp;components.&lt;/span&gt;&lt;/li&gt;
&lt;li style="font-weight:400;"&gt;Identify strategies to ensure proper handling of reusable components.&amp;nbsp;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="platform_consistency"&gt;Platform Consistency&lt;/h2&gt;
&lt;p style="font-size:115%;"&gt;&lt;span style="font-weight:400;"&gt;Ensuring applications built on the same platform have a consistent look, feel and flow is a key strategy for improving user experience and accelerating adoption. Enabling the&lt;a href="https://docs.appian.com/suite/help/20.3/using_interfaces_in_appian.html?utm_source=INTERFACELINK&amp;amp;utm_medium=Community&amp;amp;utm_campaign=APM"&gt; reuse of Appian components and interfaces&lt;/a&gt; is one way to achieve this consistency. In addition, application object reuse enables enterprise-wide programs to more efficiently deliver solutions. Reused objects in the form of complex process models, web APIs, business rules, and integrations aid the implementation teams from having to &amp;lsquo;reinvent the wheel&amp;rsquo; every time they start a new application. While maintaining reusable code does require developer attention, that maintenance actually serves as another advantage, as enhancements and bug fixes need only be implemented in one place.&lt;/span&gt;&lt;/p&gt;
&lt;h2 id="plan_for_reuse"&gt;Plan for Reuse&lt;/h2&gt;
&lt;p style="font-size:115%;"&gt;&lt;span style="font-weight:400;"&gt;Appian recommends that project teams &amp;lsquo;plan&amp;rsquo; for reuse during project kickoff &amp;ndash; sprint 0 &amp;ndash; and on an ongoing basis during the planning sessions &amp;ndash; sprint planning and design sessions. The degree to which functionalities can be reused are only limited to the amount of thought put into defining which areas should be reused in order to accelerate delivery. Teams should discuss shared interfaces early to determine which interfaces will be shared and developers can build for reuse. During the planning sessions, Appian recommends identifying business objects that may be reused within the same project/application as well as by other projects/applications within Appian as utilities and outside of Appian as web APIs.&lt;/span&gt;&lt;/p&gt;
&lt;p style="font-size:115%;"&gt;&lt;span style="font-weight:400;"&gt;Utility functions and process models are common candidates for the reusable objects; for example rules and process models that handle text/data manipulation, document generation, audit history logging, etc. Appian allows&lt;a href="/w/the-appian-playbook/2176/frequently-reused-appian-components?utm_source=FUCOMPLINK&amp;amp;utm_medium=Community&amp;amp;utm_campaign=APM"&gt; for a high degree of re-usability &lt;/a&gt;from user interfaces, integrations, processes, and business rules.&lt;/span&gt;&lt;/p&gt;
&lt;p style="font-size:115%;"&gt;&lt;span style="font-weight:400;"&gt;To foster proper change management and enhanced transparency around the reusable components built on Appian, Appian recommends naming conventions which must be clearly documented and followed by all teams. Testing and impact analysis processes are also necessary to ensure that modifications to reusable components doesn&amp;rsquo;t break other applications.&lt;/span&gt;&lt;/p&gt;
&lt;h3&gt;&lt;span class="emoticon" data-url="https://community.appian.com/cfs-file/__key/system/emoji/1f4a1.svg" title="Bulb"&gt;&amp;#x1f4a1;&lt;/span&gt;Practitioner Tip: Don&amp;rsquo;t Overlook Potential Change Management Risk&lt;/h3&gt;
&lt;p style="font-size:115%;"&gt;&lt;span style="font-weight:400;"&gt;Change Management is critical for program success. However, it is often overlooked and left until the application is ready to launch. It is important to define the change early with business and technical stakeholders, identify change agents, create the plan, pilot it and rollout to the end users. There are several factors to keep in mind here including technology transition, end user training, support needs, monitoring adoption, managing feedback from users and planning future changes.&lt;/span&gt;&lt;/p&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Delivery, Architecture&lt;/div&gt;
</description></item><item><title>Reuse Promotion</title><link>https://community.appian.com/success/w/guide/2971/reuse-promotion/revision/2</link><pubDate>Wed, 22 Mar 2023 17:10:14 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:2ca2905e-dd89-4200-a7fd-112ee18d4fe5</guid><dc:creator>Devon Lee</dc:creator><comments>https://community.appian.com/success/w/guide/2971/reuse-promotion#comments</comments><description>Revision 2 posted to Guide by Devon Lee on 3/22/2023 5:10:14 PM&lt;br /&gt;
&lt;div style="margin:8px 16% 8px 8%;"&gt;
&lt;h2 id="skills_covered"&gt;Skills Covered&lt;/h2&gt;
&lt;p style="font-size:115%;"&gt;&lt;span style="font-weight:400;"&gt;Reusing Appian components and interfaces ensures a consistent look and feel to your applications, while also promoting efficient development practices.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p style="font-size:115%;"&gt;&lt;span style="font-weight:400;"&gt;Skills Checklist:&lt;/span&gt;&lt;/p&gt;
&lt;ul style="font-size:115%;"&gt;
&lt;li style="font-weight:400;"&gt;Identify benefits to reusing Appian components and interfaces in development.&lt;/li&gt;
&lt;li style="font-weight:400;"&gt;&lt;span style="font-weight:400;"&gt;List three&amp;nbsp;frequently reused Appian&amp;nbsp;components.&lt;/span&gt;&lt;/li&gt;
&lt;li style="font-weight:400;"&gt;Identify strategies to ensure proper handling of reusable components.&amp;nbsp;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="platform_consistency"&gt;Platform Consistency&lt;/h2&gt;
&lt;p style="font-size:115%;"&gt;&lt;span style="font-weight:400;"&gt;Ensuring applications built on the same platform have a consistent look, feel and flow is a key strategy for improving user experience and accelerating adoption. Enabling the&lt;a href="https://docs.appian.com/suite/help/20.3/using_interfaces_in_appian.html?utm_source=INTERFACELINK&amp;amp;utm_medium=Community&amp;amp;utm_campaign=APM"&gt; reuse of Appian components and interfaces&lt;/a&gt; is one way to achieve this consistency. In addition, application object reuse enables enterprise-wide programs to more efficiently deliver solutions. Reused objects in the form of complex process models, web APIs, business rules, and integrations aid the implementation teams from having to &amp;lsquo;reinvent the wheel&amp;rsquo; every time they start a new application. While maintaining reusable code does require developer attention, that maintenance actually serves as another advantage, as enhancements and bug fixes need only be implemented in one place.&lt;/span&gt;&lt;/p&gt;
&lt;h2 id="plan_for_reuse"&gt;Plan for Reuse&lt;/h2&gt;
&lt;p style="font-size:115%;"&gt;&lt;span style="font-weight:400;"&gt;Appian recommends that project teams &amp;lsquo;plan&amp;rsquo; for reuse during project kickoff &amp;ndash; sprint 0 &amp;ndash; and on an ongoing basis during the planning sessions &amp;ndash; sprint planning and design sessions. The degree to which functionalities can be reused are only limited to the amount of thought put into defining which areas should be reused in order to accelerate delivery. Teams should discuss shared interfaces early to determine which interfaces will be shared and developers can build for reuse. During the planning sessions, Appian recommends identifying business objects that may be reused within the same project/application as well as by other projects/applications within Appian as utilities and outside of Appian as web APIs.&lt;/span&gt;&lt;/p&gt;
&lt;p style="font-size:115%;"&gt;&lt;span style="font-weight:400;"&gt;Utility functions and process models are common candidates for the reusable objects; for example rules and process models that handle text/data manipulation, document generation, audit history logging, etc. Appian allows&lt;a href="/w/the-appian-playbook/2176/frequently-reused-appian-components?utm_source=FUCOMPLINK&amp;amp;utm_medium=Community&amp;amp;utm_campaign=APM"&gt; for a high degree of re-usability &lt;/a&gt;from user interfaces, integrations, processes, and business rules.&lt;/span&gt;&lt;/p&gt;
&lt;p style="font-size:115%;"&gt;&lt;span style="font-weight:400;"&gt;To foster proper change management and enhanced transparency around the reusable components built on Appian, Appian recommends naming conventions which must be clearly documented and followed by all teams. Testing and impact analysis processes are also necessary to ensure that modifications to reusable components doesn&amp;rsquo;t break other applications.&lt;/span&gt;&lt;/p&gt;
&lt;h3&gt;&lt;span class="emoticon" data-url="https://community.appian.com/cfs-file/__key/system/emoji/1f4a1.svg" title="Bulb"&gt;&amp;#x1f4a1;&lt;/span&gt;Practitioner Tip: Don&amp;rsquo;t Overlook Potential Change Management Risk&lt;/h3&gt;
&lt;p style="font-size:115%;"&gt;&lt;span style="font-weight:400;"&gt;Change Management is critical for program success. However, it is often overlooked and left until the application is ready to launch. It is important to define the change early with business and technical stakeholders, identify change agents, create the plan, pilot it and rollout to the end users. There are several factors to keep in mind here including technology transition, end user training, support needs, monitoring adoption, managing feedback from users and planning future changes.&lt;/span&gt;&lt;/p&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Delivery&lt;/div&gt;
</description></item><item><title>Reuse Promotion</title><link>https://community.appian.com/success/w/guide/2971/reuse-promotion/revision/1</link><pubDate>Fri, 09 Dec 2022 16:36:25 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:2ca2905e-dd89-4200-a7fd-112ee18d4fe5</guid><dc:creator>joel.larin</dc:creator><comments>https://community.appian.com/success/w/guide/2971/reuse-promotion#comments</comments><description>Revision 1 posted to Guide by joel.larin on 12/9/2022 4:36:25 PM&lt;br /&gt;
&lt;div style="margin:8px 16% 8px 8%;"&gt;
&lt;h2 id="skills_covered"&gt;&lt;img alt=" " src="/resized-image/__size/712x304/__key/communityserver-wikis-components-files/00-00-00-00-46/reuse_5F00_promotion_2D00_02.png" /&gt;&lt;span class="sr-only"&gt;Skills Covered&lt;/span&gt;&lt;/h2&gt;
&lt;p style="font-size:115%;"&gt;&lt;span style="font-weight:400;"&gt;Reusing Appian components and interfaces ensures a consistent look and feel to your applications, while also promoting efficient development practices.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p style="font-size:115%;"&gt;&lt;span style="font-weight:400;"&gt;Skills Checklist:&lt;/span&gt;&lt;/p&gt;
&lt;ul style="font-size:115%;"&gt;
&lt;li style="font-weight:400;"&gt;Identify benefits to reusing Appian components and interfaces in development.&lt;/li&gt;
&lt;li style="font-weight:400;"&gt;&lt;span style="font-weight:400;"&gt;List three&amp;nbsp;frequently reused Appian&amp;nbsp;components.&lt;/span&gt;&lt;/li&gt;
&lt;li style="font-weight:400;"&gt;Identify strategies to ensure proper handling of reusable components.&amp;nbsp;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="platform_consistency"&gt;&lt;img alt="Platform Consistency" src="/resized-image/__size/5696x2432/__key/communityserver-wikis-components-files/00-00-00-00-46/reuse_5F00_promotion_2D00_01.png" /&gt;&lt;span class="sr-only"&gt;Platform Consistency&lt;/span&gt;&lt;/h2&gt;
&lt;p style="font-size:115%;"&gt;&lt;span style="font-weight:400;"&gt;Ensuring applications built on the same platform have a consistent look, feel and flow is a key strategy for improving user experience and accelerating adoption. Enabling the&lt;a href="https://docs.appian.com/suite/help/20.3/using_interfaces_in_appian.html?utm_source=INTERFACELINK&amp;amp;utm_medium=Community&amp;amp;utm_campaign=APM"&gt; reuse of Appian components and interfaces&lt;/a&gt; is one way to achieve this consistency. In addition, application object reuse enables enterprise-wide programs to more efficiently deliver solutions. Reused objects in the form of complex process models, web APIs, business rules, and integrations aid the implementation teams from having to &amp;lsquo;reinvent the wheel&amp;rsquo; every time they start a new application. While maintaining reusable code does require developer attention, that maintenance actually serves as another advantage, as enhancements and bug fixes need only be implemented in one place.&lt;/span&gt;&lt;/p&gt;
&lt;h2 id="plan_for_reuse"&gt;&lt;img alt="Plan for reuse" src="/resized-image/__size/5696x2432/__key/communityserver-wikis-components-files/00-00-00-00-46/reuse_5F00_promotion_2D00_03.png" /&gt;&lt;span class="sr-only"&gt;Plan for Reuse&lt;/span&gt;&lt;/h2&gt;
&lt;p style="font-size:115%;"&gt;&lt;span style="font-weight:400;"&gt;Appian recommends that project teams &amp;lsquo;plan&amp;rsquo; for reuse during project kickoff &amp;ndash; sprint 0 &amp;ndash; and on an ongoing basis during the planning sessions &amp;ndash; sprint planning and design sessions. The degree to which functionalities can be reused are only limited to the amount of thought put into defining which areas should be reused in order to accelerate delivery. Teams should discuss shared interfaces early to determine which interfaces will be shared and developers can build for reuse. During the planning sessions, Appian recommends identifying business objects that may be reused within the same project/application as well as by other projects/applications within Appian as utilities and outside of Appian as web APIs.&lt;/span&gt;&lt;/p&gt;
&lt;p style="font-size:115%;"&gt;&lt;span style="font-weight:400;"&gt;Utility functions and process models are common candidates for the reusable objects; for example rules and process models that handle text/data manipulation, document generation, audit history logging, etc. Appian allows&lt;a href="/w/the-appian-playbook/2176/frequently-reused-appian-components?utm_source=FUCOMPLINK&amp;amp;utm_medium=Community&amp;amp;utm_campaign=APM"&gt; for a high degree of re-usability &lt;/a&gt;from user interfaces, integrations, processes, and business rules.&lt;/span&gt;&lt;/p&gt;
&lt;p style="font-size:115%;"&gt;&lt;span style="font-weight:400;"&gt;To foster proper change management and enhanced transparency around the reusable components built on Appian, Appian recommends naming conventions which must be clearly documented and followed by all teams. Testing and impact analysis processes are also necessary to ensure that modifications to reusable components doesn&amp;rsquo;t break other applications.&lt;/span&gt;&lt;/p&gt;
&lt;h3&gt;&lt;span class="emoticon" data-url="https://community.appian.com/cfs-file/__key/system/emoji/1f4a1.svg" title="Bulb"&gt;&amp;#x1f4a1;&lt;/span&gt;Practitioner Tip: Don&amp;rsquo;t Overlook Potential Change Management Risk&lt;/h3&gt;
&lt;p style="font-size:115%;"&gt;&lt;span style="font-weight:400;"&gt;Change Management is critical for program success. However, it is often overlooked and left until the application is ready to launch. It is important to define the change early with business and technical stakeholders, identify change agents, create the plan, pilot it and rollout to the end users. There are several factors to keep in mind here including technology transition, end user training, support needs, monitoring adoption, managing feedback from users and planning future changes.&lt;/span&gt;&lt;/p&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;

&lt;div style="font-size: 90%;"&gt;Tags: Delivery&lt;/div&gt;
</description></item></channel></rss>