The deployment and roll-out follows the same agile principles as the development. Each MVP process scenario is deployed while the existing processes are left to handle the excluded cases. For example, specific insurance claims or purchase requisitions of a manufacturing company, in place. The kind of process execution (using RPA or using the former as-is process) is defined based on a decision table reflecting the current development status of the RPA solution and the enabled processes.

Formal testing, as with any application, is still often a critical necessity to minimise business risk. However, in more and more RPA initiatives, this risk is at least partly mitigated through the immediate execution of the process through users. If issues occur, users can still switch back to the traditional process until the RPA configuration is adjusted. Innovation becomes part of the day-to-day business. This approach is explained in figure 11.

Figure 11: Agile deployment of RPA-based processes



Leave a Comment

Want to join the discussion?
Feel free to contribute!

Leave a Reply

Your email address will not be published.