RPA projects are different from any other solution implementation projects.
Traditional solution implementation projects are based on stand alone systems. They might have integration with other systems in the organisation, but primarily the project includes an installation of a stand alone system, usually it involves PS effort to modify the system, connect it to external services and systems and define how it will react. But in the end of the day, it's a stand alone application running as any other software.
RPA projects are different by definition. There are several major difrences between RPA projects to traditional solution implimentation projects including for example:
RPA projects are based on the company's IT systems. It's an unstable environment, it is usually get changed occasionally and in general it's RPA projects built with fragile foundations which should be managed with special care.
RPA projects has no common ground. Every RPA project is different from the others and designing RPA project to support the company's targets is heavily based on consulting, guiding the business users with what can they achieve using RPA, what are the advantages and assist them with identifying the potential which is usually different from one customer to another.
In attended automation processes, the bot should assist the user to do his job better, faster and with no mistakes, and although we usually design bots to be user friendly developers tend to forget that the bot runs on the same machine as the user and they should respect the user and avoid disturbing him.
These are some examples of the RPA specific challenges which traditional solutions implementation projects doesn't have. Valor developed a unique RPA training courses training experienced PMs, BAs with RPA specific challenges, advanced training for RPA developers assisting them with designing and delivering scalable enterprise level projects etc.
For a complete list of available courses, please contact us.