
Roles and responsibilities in RPA
Assets in the iterative creation of robotic projects give different personas clear responsibilities in a development process. These personas, or roles, facilitate the best development practices, support agile planning, and ensure project quality.
Roles in the robotic project
The typical setup for a robotic project defines the following roles to cover all aspects of the project development:
-
Business Subject Matter Expert (SME): Responsible for high-level requirements and decides on technologies and building blocks to use.
-
Experienced developer: Responsible for creating and testing all possible scenarios of using the application.
-
Center of Excellence (COE) Manager: Assures the quality of the assets and adherence to best practices.
-
Robotic project manager (PM): Responsible for acceptance testing of the entire project so that it can move to production.
Note: Your organization might have divergent names for these roles and divide the responsibilities differently.
The tasks and responsibilities in project development
The following figure shows an diagram of how responsibilities among roles are divided in the robotic project:
The Business SME analyzes the functionality and possible use cases for a new application in robotic projects. The SME translates the requirements into happy path scenarios by using Intelligent Recording. As a result, the SME creates the first automations and project documentation.
The starting project with defined scenarios then goes to an experienced robotic developer, who turns them into an Application Asset. The developer extends the functionality by adding error handling and creating a test strategy for the application.
Note: At this development stage, the team focuses on testing the application behavior so that tests focus on the use cases of the project after the deployment of the Application Assets.
The developer then transfers the prepared Application Assets to the COE manager, who is responsible for a thorough review to ensure that all required standards are in place. The COE manager can approve or reject an asset based on this evaluation.
When the COE manager approves the Application Assets, the COE manager publishes the assets in the Assets Catalog. The Business SME who works on a particular project accesses the Assets Catalog from Robot Studio and can import it into a Robot Studio project.
The PM verifies the completed project that contains the assets before publishing the project to Pega Robot Manager and deploying it to production.
Check your knowledge with the following interaction:
This Topic is available in the following Module:
If you are having problems with your training, please review the Pega Academy Support FAQs.
Want to help us improve this content?