Hi Asiri,

You can go through the below course that implements a basic RDA project with a functionality and estimate the complexity of your project to decide the work force :

https://academy.pega.com/library/73/pega-robotic-automation-architect-essentials

Hi inakh,

I have done this course and have completed most of the other courses including the Pega Robotic Automation Advanced Topics. But wanted to know what are the facts I have to consider while deciding the No of developers that I have to suggest when initiation a project.

Thanks!

We generally suggest one developer works on one application that you are automating. If you have two applications that you are automating, then you could use two developers. Your developers cannot merge any common files, so coordination between them is key if there is anything shared between them (such as the Interaction.xml (if using the interaction framework). Each developer would work on automations that affect his/her application only and would test their own automations as much as required. A developer would reference each adapter project in a controlling project to orchestrate the overall automation(s). When using Robot Manager for RPA projects, the controller will be really simple and wouldn't require an extra developer. For other projects, it may be much more complex, and would benefit from having a developer work solely on the controller.