RPA Implementation Phase | Bot Development | RPA Testing | RPA Delivery Lifecycle | RPA Tutorial

What is RPA Implementation Phase? How is Bot implementation done? Who all are involved? Bot Development + Bot Testing & Bot Go-Live Planning? RPA Implementation Phase | RPA Delivery Lifecycle | RPA Tutorial

This video intent to cover in detail of entire RPA Implementation Phase. This video covers details and describe it with help of flow diagram. Please watch till end to get better consolidated understanding of the RPA lifecycle.

Bot Implementation:
Bot Development
Bot Testing ( RPA Unit testing and RPA UAT testing )
Bot Go-Live planning
RPA Code review & Bot Code review document
Unit testing document
UAT tracker
Bot user guide
Release notes
UAT & Hypercare Sign-Off
Production Readiness

What will we cover?
1. Who all are Involved?
2. How RPA Implementation process works?
3. Design Bot Solution for Potential Processes
4. Developing Best Automation Solution
5. RPA Implementation Phase? How is Bot implementation done?
6. Bot Development + Bot Testing & Bot Go-Live Planning
7. Ready for next Stage

Highlights :

Post PDD & SDD Approval, RPA Developer develops the Bot solution designed and test it for Bot run as expected.
Solution Architect performs code reviews and get necessary technical approval for Bot Go-live.
RPA Business analyst helps act as coordinator between RPA technical team & RPA Business owner/Client to get necessary Bot testing and approval on the Bot performance
Then Bot processing is reviewed & Approved, Go-live plan is prepared/revised basis which production phase get initiated.
Production Readiness should be taken care in the RPA Implementation Phase.

With approved Bot & Go-Live Plan, Production Phase gets initiated.

RPA coding best practices :
It is the standards to be followed while developing Bot so that it is easy for any other developer or support person to maintain it in future.

Few benefits of following best practices:
1. Easy handover b/w developer to developer,
2. Fast support transition,
3. Easy Bot readability & maintenance
4. Reduced Dev effort for similar process

Based on these best practices, Code review document is prepared.

Ideal RPA code should follow as below:
1. Compliance
2. Confined
3. Configurable
4. Reusable
5. Scalable
6. Robust


RPA Code review compromises of the list of industry coding standard practices at Task/Command level used to evaluate the developed code & help maintain uniformity across organization.

Code review document usually includes:
1. Checklist basis code category & Sub-category,
2. Developer & SA feedback listing basis below:
3. Task name
4. No. of instance
5. Action needed

Code review document serves as an agreement between the RPA developer & Solution Architect on the development practices.

Industry coding standards should be followed for long run benefits (Easy Bot handover/maintenance)
UAT/Prod Infra readiness should be targeted to complete while development phase to avoid any delay in UAT/Hypercare phase
Bot performance in UAT & Hypercare should be reviewed and signed off before production run


What Next?
We will discuss in detail about the Production & Support Phase.

Read RPA Blogs : https://techieonwheels.wordpress.com/
Follow me on LinkedIn:   / ritika-raj-8486088a  

#RPA #RPAImplementationPhase #BotDevelopment #RPATutorial

#rpa #rpalifecycle #rpaphases #rpacodereview #solutiondesigndocument #sdd #bot #rpadeveloper #rpatraining #hypercare#rpasolutionarchitect #rpasolutiondesigns #rpasolutiondesign #solutionarchitect #processdesigning#solutiondesign #implementation #deployment #RoboticProcessAutomation #RPATraining #RPACareer #rpa #rpabasics #rpadeveloper #whyrpa #automation #automationanywhere #uipath #blueprism #rpacommunity #rpatools #rpaqueries #BA #businessanalyst #developers #rpacoe #techieonwheels #ritikaraj