https://community.appian.com/success/w/article/2992/delivery-process-overviewen-USTelligent Community 12https://community.appian.com/success/w/article/2992/delivery-process-overviewTue, 23 Apr 2024 12:50:06 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:69d67e4c-8c84-427c-9ac7-ecbd18455cb3Appian Max Teamhttps://community.appian.com/success/w/article/2992/delivery-process-overview#commentsCurrent Revision posted to Article by Appian Max Team on 4/23/2024 12:50:06 PM<br /> <div> <p><img style="display:block;margin-left:auto;margin-right:auto;width:100%;" alt=" " src="/resized-image/__size/1189x669/__key/communityserver-wikis-components-files/00-00-00-00-45/deliveryProcess.jpg" /></p> <p>The Appian Delivery Methodology is organized into four phases: Initiate, Build, Release and Optimize.</p> <h2><b>Initiate</b></h2> <p>During the Initiate phase, frequently called &ldquo;Sprint 0&rdquo;, the team will define the goals of the project, explore what the application must do to reach those goals, and map out a plan to deliver value quickly. This is accomplished through collaborative sessions with stakeholders from across business and IT. This ensures every point of view is included and stakeholders are aligned around a common goal. The intent is not to define every project detail, but rather to perform enough planning and design to get started in the right direction. As a result, teams usually complete these activities in one to two weeks.</p> <h2><b>Build</b></h2> <p>The team builds the application in rapid iterations, usually two weeks in length, where a subset of features go through the full development cycle, with development and business quality-checks built into each iteration. The build process facilitates continuous collaboration between the development team and stakeholders.</p> <img style="width:100%;" alt=" " src="/resized-image/__size/820x546/__key/communityserver-wikis-components-files/00-00-00-00-45/deliveryGraphic.png" /> <h2><b>Release</b></h2> <p>Before the team releases the application to the business, they perform a final validation of the functionality and ensure stakeholders are ready to accept it. By leveraging testing and deployment automation, and by keeping releases small, teams can perform this phase in hours rather than days. End users are prepared and trained for usage of the new software. A short one or two week &ldquo;hypercare&rdquo; period will make sure an initial influx of support requests can be properly managed.</p> <h2><b>Optimize</b></h2> <p>After release, the team will optimize the solution&#39;s value over time, as business needs evolve, and accelerate the organization&#39;s ability to deliver value even faster in the future. Also, in this phase the team plans out the support model for the solution. The team measures the impact of the application after launch against target key performance indicators defined during the initiation phase. Also, don&rsquo;t forget to document your story to celebrate your success!</p> </div><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: Delivery</div> https://community.appian.com/success/w/article/2992/delivery-process-overview/revision/3Wed, 14 Feb 2024 20:23:37 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:69d67e4c-8c84-427c-9ac7-ecbd18455cb3joel.larinhttps://community.appian.com/success/w/article/2992/delivery-process-overview#commentsRevision 3 posted to Article by joel.larin on 2/14/2024 8:23:37 PM<br /> <div> <p><img style="display:block;margin-left:auto;margin-right:auto;width:100%;" alt=" " src="/resized-image/__size/1189x669/__key/communityserver-wikis-components-files/00-00-00-00-45/deliveryProcess.jpg" /></p> <p>The Appian Delivery Methodology is organized into four phases: Initiate, Build, Release and Optimize.</p> <h2><b>Initiate</b></h2> <p>During the Initiate phase, frequently called &ldquo;Sprint 0&rdquo;, the team will define the goals of the project, explore what the application must do to reach those goals, and map out a plan to deliver value quickly. This is accomplished through collaborative sessions with stakeholders from across business and IT. This ensures every point of view is included and stakeholders are aligned around a common goal. The intent is not to define every project detail, but rather to perform enough planning and design to get started in the right direction. As a result, teams usually complete these activities in one to two weeks.</p> <h2><b>Build</b></h2> <p>The team builds the application in rapid iterations, usually two weeks in length, where a subset of features go through the full development cycle, with development and business quality-checks built into each iteration. The build process facilitates continuous collaboration between the development team and stakeholders.</p> <img style="width:100%;" alt=" " src="/resized-image/__size/820x546/__key/communityserver-wikis-components-files/00-00-00-00-45/deliveryGraphic.png" /> <h2><b>Release</b></h2> <p>Before the team releases the application to the business, they perform a final validation of the functionality and ensure stakeholders are ready to accept it. By leveraging testing and deployment automation, and by keeping releases small, teams can perform this phase in hours rather than days. End users are prepared and trained for usage of the new software. A short one or two week &ldquo;hypercare&rdquo; period will make sure an initial influx of support requests can be properly managed.</p> <h2><b>Optimize</b></h2> <p>After release, the team will optimize the solution&#39;s value over time, as business needs evolve, and accelerate the organization&#39;s ability to deliver value even faster in the future. Also, in this phase the team plans out the support model for the solution. The team measures the impact of the application after launch against target key performance indicators defined during the initiation phase. Also, don&rsquo;t forget to document your story to celebrate your success!</p> </div><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: Delivery</div> https://community.appian.com/success/w/article/2992/delivery-process-overview/revision/2Fri, 02 Jun 2023 18:28:28 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:69d67e4c-8c84-427c-9ac7-ecbd18455cb3joel.larinhttps://community.appian.com/success/w/article/2992/delivery-process-overview#commentsRevision 2 posted to Article by joel.larin on 6/2/2023 6:28:28 PM<br /> <p><img style="display:block;margin-left:auto;margin-right:auto;width:100%;" alt=" " src="/resized-image/__size/1189x669/__key/communityserver-wikis-components-files/00-00-00-00-45/deliveryProcess.jpg" /></p> <div> <p>The Appian Delivery Methodology is organized into four phases: Initiate, Build, Release and Optimize.</p> <h2><b>Initiate</b></h2> <p>During the Initiate phase, frequently called &ldquo;Sprint 0&rdquo;, the team will define the goals of the project, explore what the application must do to reach those goals, and map out a plan to deliver value quickly. This is accomplished through collaborative sessions with stakeholders from across business and IT. This ensures every point of view is included and stakeholders are aligned around a common goal. The intent is not to define every project detail, but rather to perform enough planning and design to get started in the right direction. As a result, teams usually complete these activities in one to two weeks.</p> <h2><b>Build</b></h2> <p>The team builds the application in rapid iterations, usually two weeks in length, where a subset of features go through the full development cycle, with development and business quality-checks built into each iteration. The build process facilitates continuous collaboration between the development team and stakeholders.</p> <img style="width:100%;" alt=" " src="/resized-image/__size/820x546/__key/communityserver-wikis-components-files/00-00-00-00-45/deliveryGraphic.png" /> <h2><b>Release</b></h2> <p>Before the team releases the application to the business, they perform a final validation of the functionality and ensure stakeholders are ready to accept it. By leveraging testing and deployment automation, and by keeping releases small, teams can perform this phase in hours rather than days. End users are prepared and trained for usage of the new software. A short one or two week &ldquo;hypercare&rdquo; period will make sure an initial influx of support requests can be properly managed.</p> <h2><b>Optimize</b></h2> <p>After release, the team will optimize the solution&#39;s value over time, as business needs evolve, and accelerate the organization&#39;s ability to deliver value even faster in the future. Also, in this phase the team plans out the support model for the solution. The team measures the impact of the application after launch against target key performance indicators defined during the initiation phase. Also, don&rsquo;t forget to document your story to celebrate your success!</p> </div><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: Delivery</div> https://community.appian.com/success/w/article/2992/delivery-process-overview/revision/1Fri, 09 Dec 2022 18:09:10 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:69d67e4c-8c84-427c-9ac7-ecbd18455cb3Devon Leehttps://community.appian.com/success/w/article/2992/delivery-process-overview#commentsRevision 1 posted to Article by Devon Lee on 12/9/2022 6:09:10 PM<br /> <p><img style="display:block;margin-left:auto;margin-right:auto;width:100%;" alt=" " src="/resized-image/__size/1189x669/__key/communityserver-wikis-components-files/00-00-00-00-45/deliveryProcess.jpg" /></p> <div style="margin:10px 21% 10px 21%;"> <p style="font-size:115%;"><span style="font-weight:400;">The Appian Delivery Methodology is organized into four phases: Initiate, Build, Release and Optimize.</span></p> <h2><b>Initiate</b></h2> <p style="font-size:115%;"><span style="font-weight:400;">During the Initiate phase, frequently called &ldquo;Sprint 0&rdquo;, the team will define the goals of the project, explore what the application must do to reach those goals, and map out a plan to deliver value quickly. This is accomplished through collaborative sessions with stakeholders from across business and IT. This ensures every point of view is included and stakeholders are aligned around a common goal. The intent is not to define every project detail, but rather to perform enough planning and design to get started in the right direction. As a result, teams usually complete these activities in one to two weeks.</span></p> <h2><b>Build</b></h2> <p style="font-size:115%;"><span style="font-weight:400;">The team builds the application in rapid iterations, usually two weeks in length, where a subset of features go through the full development cycle, with development and business quality-checks built into each iteration. The build process facilitates continuous collaboration between the development team and stakeholders.</span></p> </div> <div style="text-align:center;"> <p><img style="width:80%;" alt=" " src="/resized-image/__size/820x546/__key/communityserver-wikis-components-files/00-00-00-00-45/deliveryGraphic.png" /></p> </div> <div style="margin:10px 21% 10px 21%;"> <h2><b>Release</b></h2> <p style="font-size:115%;"><span style="font-weight:400;">Before the team releases the application to the business, they perform a final validation of the functionality and ensure stakeholders are ready to accept it. By leveraging testing and deployment automation, and by keeping releases small, teams can perform this phase in hours rather than days. End users are prepared and trained for usage of the new software. A short one or two week &ldquo;hypercare&rdquo; period will make sure an initial influx of support requests can be properly managed.</span></p> <h2><b>Optimize</b></h2> <p style="font-size:115%;"><span style="font-weight:400;">After release, the team will optimize the solution&#39;s value over time, as business needs evolve, and accelerate the organization&#39;s ability to deliver value even faster in the future. Also, in this phase the team plans out the support model for the solution. The team measures the impact of the application after launch against target key performance indicators defined during the initiation phase. Also, don&rsquo;t forget to document your story to celebrate your success!</span></p> </div><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: Delivery</div>