Automation impact

End-to-End RPA explained
in simple words

Automation impact

End-to-End RPA explained
in simple words

AI4 – Development Standards – Part 1

AI4 - Developments Standards - Part 1

Topic: Development standards
GuestRadomir Ivankovic
Recommended for: RPA developers, RPA Lead, 
CoE management

Development Standards - Part 1

The Script of the Episode:
   00:50 Radomír’s story and background
   09:11 Working with UiPath – journey to MVP role
   13:30 Recommendations for future MVP’s
   18:11 Importance of Development Standards (for non-developers as well)
   20:31 Radomír’s experience with building Development Standards
   23:50 Learning among the journey
   27:45 The basic standards
   37:08 The good standards
   43:38 Advanced standards

About the Guest: Radomír Ivankovic – RPA CoE Lead Developer @ OLX Group, Germany
Radomír is one of the UiPath MVP, has a bachelor’s degree in Electrotechnical Engineering and Computer Science. As he puts it, he’s always loved technology – even back in time when the internet was still dial-up. Radomír started with automation as a Linux administrator in NCR. He has automated a 20 minutes long process into 30 seconds and saved the company around EUR 1.5M . This became the origin of RPA in NCR. After that, Radomir got an offer in Berlin with the BASF where was covering senior RPA developer role. Then moved to OLX. The work in OLX is “more free and also more chaotic but here he had the opportunity to try whatever he wanted”. It brought several new challenges for Radomír that include Chatbot and AI Fabric. As an MVP himself, Radomír suggests for developers to focus on engagement with the community and exploring new things.

First of all, development standards are not only important for developers themselves but also project managers and RPA champions. Main reason is that project champions need to have an understanding what the right standards are to don’t be confused when external and internal developers step in and try to convince that all the bot failings is just a nature of RPA but not their fault. 

As per Radomir, common mistake is that companies are hiring developers first when beginning with RPA. They should first hire Business Analysts so they would map processes, create PDD, create measurement, and see how often that process is done, how much money it will save.

The basic standards – minimal must have:

  1. You must have standards! They can be wrong but they need to be in place.
  2. You must have 3 environments: development, test, production.
  3. All robots should have the same level of access.
  4. Never work in production.
  5. Optimize then automate.

The good standards – golden middle & strong basics:

  1. Admins in systems need to keep their sandbox environment up to date.
  2. Always have a dispatcher.
  3. Use switch instead of nested “if”.
  4. Standards for BA need to be set.
  5. Educate whom you are working with.

Advanced standards – very nice to have things applicable to the senior team:

  1. Use Agile as a delivery methodology
  2. Have a deadline, not working hours.
  3. Advanced Framework, changes to normal reFramework.