UiPath Community: Mindful RPA Methodology

What is the purpose of this event?
Explore an alternative view and approach to Robotic Process Automation (RPA) as we discuss the E-Book "Mindful RPA Methodology" with the creator and author Djuro Ivankovic. This innovative but obvious approach emphasizes user involvement, segmented deployment and continuous improvement, ensuring your automation projects are efficient, effective and user-friendly. This session will delve into practical tools, techniques, and strategies that can enhance your RPA implementations. Whether you're a business analyst, project manager or RPA professional, this event will provide you with valuable insights to drive successful RPA projects in any organization.

Who can join?
This event is open to all RPA enthusiasts, business analysts, project managers, and professionals involved in the automation journey. Our goal is to deliver high-quality content that caters to both business and functional leaders. Whether you're at the conception phase of your automation journey or looking to scale and optimize existing processes, this event offers valuable insights and practical advice. Join our community of automation experts and market participants to share experiences, grow together, and achieve successful RPA implementations.

Agenda
Our meetup will focus on the following topics:
Understanding the Mindful RPA Methodology
Tools and Techniques - Best Practices
Introducing Streamlined Development and Parallel Productivity
Challenges and Solutions
Discussion, Q&A
We look forward to bringing this methodology to you and to having interesting discussions with you! Feel free to download the free E-Book beforehand: https://rpa.rs/product/mindful-rpa-methodology/

1. Mindful RPA
Methodology

2. 2
•Understanding the Mindful RPA Methodology
•Introducing Streamlined Development and Parallel Productivity
•Tools and Techniques -Best Practices
•Challenges and Solutions
•Discussion, Q&A
Agenda

3. 3
Djuro Ivankovic
Creator Of RPA Methodology & Freelance Consultant
UiPath MVP
“In order to move you need to walk,
in order togrow you need to talk.”
LinkedIn RPA.rs

4. 4
ROMAN TOBLER
CEO and Owner @Routinuum
UiPath MVP and Zurich RPA Community Chapter Leader
Author of Excelblog.ch(mainly in German)
LinkedIn Routinuum Excelblog.ch

5. Mindful RPA Methodology

6. 6
Overall, the Mindful RPA Methodology is designed to provide a systematic
and flexible approachto RPA project management that prioritizes user
trust, communication, and cost management.
Mindful RPA Methodology –Overall
“
”

7. 7
Through the Mindful RPA Methodology, teams can deliver projectsfaster,
reduceunnecessary documentation, eliminateunnecessary costs, and
improve communication.
By focusing on communication and explaining the importance of project
segmentation, the team can work more efficientlyand develop stress-free.
Benefits and Focus Points
“
”

8. 8
RPA-Awareness & Change Management
Awareness / Know
-
How
Time (t)
Details:
C-Level / Initiator
Process Owners
SME

9. 9
Another challenge is that users fear that the bot will take over their job, and in
most cases, cooperation with SME is not smooth. After the bot is deployed,
every single mistake will be flagged, but not as a ticket to be fixed; rather,
people point fingers at the bot, trying to make it look unreliable.
Fear, Uncertainty –and Finger-Pointing
“
”

10. 10
Another key principle […] is early testing and involvement of users. This
ensures that real problems are discovered early on in theproject and that the
bot is stable and reliablefrom the very beginning. This also allows for
continuous feedback and improvement throughout the development process.
User Involvement & Feedback
“
”
Involving users from the beginning as testers will ensure that they accept the
automationrather than reject it as a threat to their jobs.“
”

11. 11
➔How do you approach users or departments that are new to the Automation Initiative?
User Involvement –Scope& Tasks
This could include working on low-priority automation projects,
or undertaking other tasks that will support the RPA team in the
long run, such as writing documentation, organisingreusable
components, or exploring new opportunities for automation.
“
”

12. 12
Once the PDDis finalized, the RPA team should get a sign-off from the user team,
which indicates their agreement to proceed with development. The RPA team
should then prioritize the project and create a detailed development planwith
specific deadlines and milestones.
[…] Then, follow the plan.
The Process ofAutomation
“
”
➔Benefit: Segmentation also leads to earlier savings reporting[...] from the first
deployment because the user has started using some part of the bot.

13. 13
Dolphin Head vs. Hockey Stick Effect

14. Tools and Techniques

15. 15
•RPA PLATFORMS
•TASK MINING
•PROCESS MAPPING
•REQUIREMENTS GATHERING
•AGILE METHODOLOGIES
•TESTING AND QUALITY ASSURANCE
•DEPLOYMENT AND MONITORING
Tools and Techniques

16. 16
Based on my experience, weekly meetings may not be enough for larger
teams, while daily meetings may be too frequent for smaller teams. A good
compromise could be to have meetings on Monday, Wednesday, and Friday.
On Mondays, the team can plan the week ahead and give updates on the
items they will work on.
On Wednesdays, a short standup can be held where each team member is
asked one question: "Do you have any problems?" Those who don't have any
issues can drop off, while those who have problems can stay to discuss
potential solutions.
Finally, on Fridays, the team can wrap up the week, review on-going tickets vs
closed tickets, and plan for the next sprint.
Focus: Agile Methodologies
“
”
“
”

17. 17
•Differences between attendedand unattendedcases?
•For attendedcases: How can a user know what the Bot is currently doing?
-Counts for both Foreground/UI Activities, but also/especially Background
Activities.
→See following example: StatusProgressBar
Testing & User Involvement

18. 18
ActivityPackage: «UiPathTeam.StatusProgress.Activities»
AttendedCases: StatusProgress

19. 19
AttendedCases: StatusProgress–Example

20. 20
AttendedCases: StatusProgress–Example

21. Challenges and Solutions

22. 22
Users
1.The unresponsive user who is not utilizing automation parts and not
providing testing
2.Too responsive SME who has many ideas for changes and deviations from
the signed project
3.Resistance to change, where some employees may resist the adoption of
RPA
Management & Expectations
Not being able to deliver and fulfill expectations for various reasons...
… a fewchallengesthatonecanface

23. How to collaborate…

24. 24
UiPath Forum Post:
https://forum.uipath.com/t/mindful-rpa-methodology/569805
… orreachout directlytoDjuro.
Mindful RPA Methodology –Collaboration

25. Discussion