Project Management

Please login or join to subscribe to this thread

RPA Project support?

linkedin twitter facebook  
avatar
Chamnab Nhel University of the Cumberlands Mn, United States
Dear all networks,

I am looking for support/advice for the RPA project. I am very new to RPA technology, and I am currently assigned to lead an RPA project for a commercial bank bank-wide process improvement. Thanks, and appreciate it if you could share your experience on the RPA project.
Sort By:
avatar
Stéphane Parent Self Employed / Semi-retired| Leader Maker Prince Edward Island, Canada
All the best with your robotic process automation project, Chamnab.
avatar
Abolfazl Yousefi Darestani Manager, Quality and Continuous Improvement| Hörmann-TNR Industrial Doors Newmarket, Ontario, Canada
No RPA experience here. Good luck
avatar
Keith Novak Tukwila, Wa, United States
Robotics requires some very sophisticated engineering including mechanical, electrical, computer science, and control systems. If you are not well versed in the discipline than I would suggest considering your top down organization structure where the PM is assigned a senior engineer in a system architecture role.

You won't have time to become a technical expert and lead the project. The chief engineer (or whatever you call the role) will have primary responsibility for technical organization and development lifecycle. The PM aligns the technical plan to the organization's business plan. You will need to communicate closely with that person as you need to learn about how critical technical decisions steer the project plan and how business drivers like cost and time to delivery also steer the technical decisions.

Sometimes a project engineer can be one part senior engineer and one part PM, but on larger more complex projects, there is too much work to do both roles effectively.
...
1 reply by Kiron Bondale
Feb 13, 2023 2:51 PM
Kiron Bondale
...
The RPA which Chamnab is referring to doesn't require any hardware (normally) - it is basically replacing manual procedures performed across multiple desktop applications with automation.

Chamnab, having been involved with one reasonable sized RPA program in my last contract role in the financial services space, the one thing I would recommend is to spend sufficient discovery time upfront for each business process to ensure that your team is capturing the actual way in which the work is done and understands environment-specific differences (e.g. desktop to deskop, production vs test) before committing to a timeline or cost estimate for conversion.

Kiron
avatar
Verónica Elizabeth Pozo Ruiz RYLAI Access Control Quito, Pichincha, Ecuador
You must review concepts about RPA, to acquire general technical knowledge about the matter of the project.

* https://www.mdpi.com/2071-1050/14/3/1333
* https://www.q3edge.com/robotic-process-automation/
avatar
Kiron Bondale Retired | Mentor| Retired Welland, Ontario, Canada
Feb 13, 2023 11:02 AM
Replying to Keith Novak
...
Robotics requires some very sophisticated engineering including mechanical, electrical, computer science, and control systems. If you are not well versed in the discipline than I would suggest considering your top down organization structure where the PM is assigned a senior engineer in a system architecture role.

You won't have time to become a technical expert and lead the project. The chief engineer (or whatever you call the role) will have primary responsibility for technical organization and development lifecycle. The PM aligns the technical plan to the organization's business plan. You will need to communicate closely with that person as you need to learn about how critical technical decisions steer the project plan and how business drivers like cost and time to delivery also steer the technical decisions.

Sometimes a project engineer can be one part senior engineer and one part PM, but on larger more complex projects, there is too much work to do both roles effectively.
The RPA which Chamnab is referring to doesn't require any hardware (normally) - it is basically replacing manual procedures performed across multiple desktop applications with automation.

Chamnab, having been involved with one reasonable sized RPA program in my last contract role in the financial services space, the one thing I would recommend is to spend sufficient discovery time upfront for each business process to ensure that your team is capturing the actual way in which the work is done and understands environment-specific differences (e.g. desktop to deskop, production vs test) before committing to a timeline or cost estimate for conversion.

Kiron
avatar
Latha Thamma reddi Sr Product and Portfolio Management (Automation Innovation)| DXC Technology Mckinney, Tx, United States
Thanks for sharing.

Please login or join to reply

Content ID:
ADVERTISEMENTS

I see where one young boy has just passed 500 hours sitting in a treetop. There is a good deal of discussion as to what to do with a civilization that produces prodigies like that. Wouldn't it be a good idea to take his ladder away from him and leave him up there?

- Will Rogers

ADVERTISEMENT

Sponsors







Vendor Events

See all Vendor Events

Newsletters

Jun 3: The Career Problem Facing New PMs
May 20: Your PM Career as a Project Life Cycle
May 13: The Big Lie After Layoffs

See all newsletters