Building an RPA solution, unfortunately, doesn’t fit the idea of a single house or multiple same houses either. RPA is a bit specific. Sometimes you have all the requirements in advance but still, there might be minor changes during the journey. As well the user interface of third-party applications might change. But usually, there are no big changes in the business processes we need to automate. And that’s the power of RPA too, remember? You don’t need to adjust the business process anyhow.
So based on those information in our opinion is the wisest way is to do a little bit of this and a little bit of that. The idea is to have a Waterfall approach with Agile components. Like a showcase for example, when you meet with the client on regular basis to demonstrate, what did you do so far and how exactly it works. So you can be sure, that if there are any adjustments needed, you know about that as soon as possible. But there is no reason, to go fully Agile because as we said already, the processes are defined and requirements should be set.
As well as bigger changes in our workflow could affect more than a single component. An important thing to keep in mind is that a difference between creating an application and creating an RPA automation is, that in our app it can go through functions like 1 – 3 – 1 – 5 – 1 based on user requirements. But the automation of a process is linear, because the process is always the same, so it’s more like 1 – 2 – 3 – 4 – 5. For that reason, if we make a change in point 2, it might affect points 3, 4, and 5 as well.