RPA Governance - Project LifeCycle

Project Phase	Project Deliverable	Summary	Assigned To	Relevant Documentation	Storage Location (Short Term)
Identify and Prioritize	Business Case	Analyze the Volume and Processing Time, Risk Impact, Customer Experience Impact, and Associate Impact of a process to determine the size of opportunity for the use case	Business Analyst	Business Case Template	UI Path
	Current State Process	Document the Current State at a high level including Systems, Handoffs, High Level Steps, Triggers, and overall objective of Process	Business Analyst	Visio Process Map	Teams
	Identify System Access	Determine all relevant systems in Process to ensure System Accounts (bots) can access those systems	Business Analyst	System Access Matrix	Automation Hub
	Feasibility Analysis	Perform a feasibility analysis to determine if the process is ripe for automation, and to confirm that RPA is the correct tool for the problem	Business Analyst	Feasibility Tracker	Automation Hub
	Prioritization of Project	Determine where this project should be slotted against other processes	RPA Manager		N/A
Design	Future State Process	Design the future state process, including what steps the bot will automate, and what steps will remain manual for Process Owner	Bot Owner	Visio Process Map	Teams
	Requirements Document	More in-depth analysis of the process steps to understand each individual step and the exception paths that exist	Business Analyst	Requirement Document Template	Teams
	Process Owner Signoff	Process Owner to review the requirements document and signoff for completeness/correctness	Process Owner		N/A
	Developer Signoff	Developer to review the requirements document and signoff for completeness/correctness	Developer		N/A
	System Account Access	Get System Accounts Access to the required Systems before development begins	Bot Owner		N/A
	Developer Account Access	Get Developer(s) Access to the required Systems to begin development	Bot Owner		N/A
	Distribution List for Bot Emails	List of people who should receive the bot notifications/emails	Bot Owner	N/A	N/A
	FMEA (Failure Modes Effect Analysis)	Perform Risk Analysis on Process to find risk points and embed controls within Automation	Bot Owner/Process Owner/Developer	FMEA Template	Teams
	Data Usage/Storage Documentation	Document the data being used/stored by the bot to ensure PII protection	Bot Owner	Data Storage Matrix	Teams
	Machine Capacity/Allocation	Determine how much Capacity automation will require, and schedule this time against other bots	RPA Manager	Bot Schedule	Teams
Development	Update/Leverage Code Repository	Leverage Code Repository to re-use tasks and add tasks for other projects	Developer		UI Path
	Login to WinSCP	Develop Code	Developer		UI Path
	Get File	Develop Code	Developer		UI Path
	Format File	Develop Code	Developer		UI Path
	Login to Concur	Develop Code	Developer		UI Path
	Upload File	Develop Code	Developer		UI Path
	Validate Upload of File	Develop Code	Developer		UI Path
	Move File	Develop Code	Developer		UI Path
	Error Handling	Error Handling so bot will behave correclty if task is to fail	Developer
	Code Review Checklist/Peer Review	Follow Code Review Checklist to ensure standards are being met and get signed off by another developer	Developer	Code Review Checklist	Teams
	Code Documentation	Document Code so another developer can understand and make changes if required in the future	Developer		Teams
	Recording of Bot Execution	Record bot execution to share with stakeholders and review how the bot works	Developer	Bot Recording	UI Path
Testing	Development of Test Scripts	Develop Test Scripts to determine all the scenarios/steps that need to be validated to ensure the bot is working correctly	Bot Owner/Process Owner/Developer		Teams
	Provide Test Data	Provide Test Data for developer to run to ensure all the test scripts can be completed	Process Owner/Bot Owner		Teams
	Test Execution	Developer to run the code and ensure all the tests are completed	Developer		UI Path
	Migrate and Execute Bot on UAT Machine	Migrate bot to UAT machine by pushing package through Orchestrator	Developer		N/A
	Process Owner Test Signoff	Process Owner to review Test Results/Evidence and ensure that the tests are passed	Process Owner		N/A
Pre-Production Readiness	Release Management Governance Checkpoint	Review Governance and Test Scripts with Leadership before pushing code to Production Parallel	RPA Manager		N/A
Production Parallel	Production-Parallel Data	Process Owner to provide Production Parallel Data (if applicable) for bot to process along with agents to determine the results are the same (have bot NOT submit data if applicable)	Process Owner		Teams
	Production-Parallel Tracker	Store the results of the production-parallel as evidence of completion/correctness	Bot Owner	Prod-Parallel Tracker	Teams
	Push Code to Production Machine	Push the code to Production Machine by pushing package in Orchestrator	Bot Developer
	Production Parallel Process Owner Signoff	Process Owner to signoff on the bot results before launching bot to production	Process Owner		Teams
	Release Management Governance Checkpoint	Provide above Production Parallel Data/Results to Leadership for Signoff before moving bot to  Production	RPA Manager		Teams
Go-Live	Stakeholder Communication	Communicate with Stakeholders the Go-Live date and plan for Go-Live	Bot Owner		N/A
	Go-Live Date Agreed	Date of Go-Live	Bot Owner/Process Owner		N/A
Post Production Support	ROTA	Who is responsible for support of bot at different times and determine criticality of support for Business Process	Support	ROTA Template	Teams
	Password Maintence	Update Passwords as needed for Process	Support		Teams
	Bug/Enhancement Identification and Backlog	Manage the Documentation and Requirements of Identified Bugs and Enhancements	Support	Microsoft Dev Ops
	Documentation of Common Issues/Resolutions	Document common issues and resolutions for support of the automation	Support	Support Template	Teams
	Code Patches and Implementation	Update and patch code for resolution of issues	Support		N/A