I’d like to know how you go about contracting for an RPA project.
In Korea, contracts are executed without conducting accurate calculations and business identification during the contract process, resulting in a lack of schedule and stability, which leads to a decrease in customer satisfaction, and in addition, the market seems to be dying due to the increase in license fees.
I would like to know how the contracting process, public estimation, and task identification are carried out in each country, and what human resources are invested in a project. eX) Developers, planners, PMs, etc.
I’m also curious about the order of RPA projects and the market in each country.
Hi @111617 ,
RPA projects as well as other software projects such as apps and websites…
However, you need to clearly define the specific project, for example, calculate the price based on the number of robots or the entire project
In Vietnam, I used to work on banking projects. I learned that there are 2 types of contracts.
One is calculated based on the number of robots, and the level of robots is evaluated based on the complexity of the number of interacting systems…etc.
The other type is calculated by project without fixed time and number of robots. For these projects, it will be calculated according to manday, project wbs agreed and agreed between customers.
regards
RPA is a fairly new field in Vietnam, about 6-7 years ago
I think in Korea it is also a new field, right?
Just like other software projects such as mobile app or website…
We also have Product, outsourcing, offshore models, etc.
The characteristic of RPA is that a project is usually quite small, I often call it a process, 1 robot performs that process.
Here, building a robot for a process can also take a team, but the team size is usually small, a few people.
In large companies, we still assign roles in projects such as PM, BA, dev, test, customer support,… One person can only do one position with freshers and juniors. However, at the senior and higher levels, one person can completely do a process from start to finish, perfecting a robot from start to finish.
This person can work as a PM to plan the project and estimate the time to complete each phase. Can meet customers, get requests, create PDD/SDD/DSD documents… like BA. You can also implement code yourself like a Developer. Can also test and create test documents like a tester.
Support publishing and answering questions, creating user documentation for customers.
In my opinion, with RPA characteristics, one person should complete all steps, or coordinate from a small group of 2-3 people.