In traditional software development projects, business and technology are complementary and indispensable. No matter how clear the business is, the technology cannot be realized, or no matter how high the technology level is, the business is in a mess, it can’t be completed successfully.
However, in traditional development projects, the division of labor between them is relatively clear. Business has its own domain, which requires the participation of people with certain business background (BA). Technology also has a certain degree of professionalism, which also requires the participation of technical background personnel (SA). The two belong to mutual cooperation and cooperative operations.
However, some projects that are not very business oriented do not need professional business personnel (BA) to participate. Some SA who understand business can complete independently.
So, in RPA projects, business or technology?
The author mentioned in the article “how to build RPA special forces quickly for enterprises” that RPA projects need special operations, small, quick, stable, accurate and ruthless. Therefore, to have a strong individual combat capability, RPA practitioners need to understand technology and business, that is, the more popular compound talents.
Now there is a misunderstanding in the market that RPA project is relatively simple, and people without programming foundation can do it. Drag and drop can be easily done. Some RPA manufacturers also exaggerate the publicity and advertising effect, saying that business personnel can master RPA completely; others say that RPA tools are just like office software, which can be easily used by everyone.
Some business people will also think that RPA project is a combination of business, drag and drop the components needed to connect them together, which is not very complex. As a business person, it can also be done. These understandings are that the system and details of RPA project are not well understood. To put it bluntly, we only see the surface, not the essence, and only grasp some basic concepts and simple operation steps. Everyone who studies programming can make a small program. Does the ability to make a small program mean mastering a language?
Although RPA tool provides rich functional components, and the operation steps are drag and drop, it is only the most basic operation mode, that is, the first step has just been taken, and there are many steps to complete in the future.
The process can run and run through is just the beginning. In the process of development, we need to consider all kinds of special circumstances, the handling of exceptions, how to connect the upstream and downstream data, whether to use the optimal scheme, and how to optimize your code, which is robust, safe, general and easy to maintain.
RPA project follows the process of software development, has a special framework, a general component library, a unified code storage, a strict coding manual and coding specifications. These corresponding requirements or specifications, if not practiced and precipitated in the field of traditional software development for several years, are difficult to achieve.
There is also a lack of risk awareness. There are absolute advantages and disadvantages in doing high-risk things. For example, stocks and futures are the fastest way to make money, but if they are not properly operated, they will lose their money. How to make money while avoiding risks is the most important thing.
RPA projects also face the risk of potential business data errors. For customers, RPA tools are the most effective way to improve production efficiency and correctness. However, if business data is wrong due to poor consideration or defects, it is just the opposite.
It’s undeniable that some business people can develop simple RPA processes, but I’m not sure if they have full confidence in the code quality without the above development system and experience guarantee? Dare to put the process into production? Is it possible to ensure that there are no errors in operation? And in the face of problems, can quickly solve the problem? Is there a backup mechanism? Who will maintain and upgrade the code?
As a professional RPA team, we carried out RPA projects in China earlier. In fact, our requirements for developers are also very high. I’ve interviewed hundreds of candidates since 2015. To become a member of our team, the prerequisite is technical development background, which can be Java or C, with 1-3 years, 3-5 years and more than 5 years of working experience. According to the observation and assessment in all aspects of the work over the past four years, I found that the developers who are really able to do their own work (good technology, business know-how) are still the group of developers with about five years of development experience.
At present, RPA tools on the market are the combination of functional components and technical implementation, which cannot be separated from technical implementation in a short time. Because RPA’s business process is not very complex, it is not difficult for developers with certain experience, plus some experience in process improvement, to be independent. However, it is very difficult for business personnel to reach the project landing by mastering the operation of RPA tools. The value of business personnel is more reflected in the carding of business processes, and then the real RPA requirements of these businesses can be discovered, which can accurately feed back to the RPA development team.
What’s more, being able to do RPA is totally different from being able to do RPA well.
In a word, it is the right way to let professional people do professional things, so as to better promote the healthy development of RPA industry.