The Implementation Methodology Model - Handout

Download as pdf or txt
Download as pdf or txt
You are on page 1of 5

UiPath

Automation
Implementation
Methodology
Fundamentals
The UiPath Implementation Methodology Model
Stage Roles Involved Key Task Output

• Solution • Setting up the overall • Reviewing and


Architect expectations of the project signing off the
SOW
• Project • Conducting early RPA
Manager readiness discussions • Setting up
about communication
Kickoff
• Infrastructure cadence
Engineer − Client’s environment
and infrastructure • Completing the
customer readiness
− Test and dev checklist
environments
• Initiating the Issue
− Test data/test cases Tracker

• Solution • Assessing potential • Verifying the


Architect automations for their automation use
complexity and feasibility case
• Project
Manager • Validating the estimated • Confirming use
timelines and efforts case alignment with
• Business required for successful contract
Analyst delivery expectations
Business Case
and Technical
Validation • Validating the business
case for the selected use
cases and the Cost-Benefit
part of it

• Identifying the key


complexity, technical
dependencies, and access
to key applications

• Solution • Analyzing the chosen • Defining and


Architect process in its as-is state finalizing the ‘to-be’
and drafting the PDD process
• Project
Manager • Identifying the degree of • Completing and
Process automation approving the PDD
Analysis • Business
Analyst • Streamlining the business • Creating and
flow to the ‘to-be’ process approving the UAT
plan
• Filling in the PDD with the
as-is and to-be processes

UiPath Implementation Methodology Model 2


• Solution • Designing a future state • Completing the SDD
Architect flow and mapping out the document
modules for automation
• Project development • Completing the
Manager Application Tracker
• Using the Application
• Automation Tracker to record access • Completing the
Solution Developers required by the developer to Technical Testing Plan
Design build and run automation in
UAT and Production

• Preparing the Technical


Testing plan encompassing
UAT scenarios, functional
testing, and system
integration testing

• Solution • Creating the modules • Building the automation


Architect outlined in the design
whiteboard using the PDD • Completing Unit and
• Project and SDD Integration Testing
Manager
• Reviewing and making • Completing code review
• Automation necessary changes to the
Developers code • Executing the Technical
Testing plan
• Testing and running the
modules individually in
controlled settings

• Executing the Technical


Development
and Testing Testing plan after
Development and Unit
Testing

• Creating automated tests


for functional testing to
confirm large functions work
independently

• Completing the end-to-end


test for system integration
testing

• Running all UAT test


scenarios

UiPath Implementation Methodology Model 3


• Solution • Conducting UAT in • Executing UAT Test
Architect coordination with the Cases
Implementation Team
• Business • Signing off client
Analyst • Running all the potential business team test
happy-path and business execution
• Project exception scenarios
Manager • Completing the
• Ensuring all agreed-upon Runbook document
• Automation scenarios are tested
Developers
• Logging any defects/bugs
and having them fixed

• Creating a Runbook
document template with the
following details:
User
Acceptance
Testing (UAT) − System architecture

− Production
environments

− Operating instructions
for automation

− Instructions to the
Operations, IT, and
Implementation Team

• Adjusting Runbook during


Hypercare

• Documenting the Runbook


template for every
automation

• Solution • Migrating the final process • Revising the Runbook


Architect packages, libraries, and document
assets to the production
• Project Orchestrator • Completing production
Manager bug fixes
Deployment • Identifying and addressing
and Hypercare • Automation issues quickly using
Developers Hypercare

• Running and reviewing


production cases using
Hypercare

UiPath Implementation Methodology Model 4


• Fixing issues promptly and
re-pushing to production

• Initiating knowledge transfer


during Hypercare

• Solution • Confirming conformance of • Checking and


Architect all services are made as signing off contract
per the contract completion by the
• Project client
Manager • Carrying out the handover
process for long-term • Initiating knowledge
• Business support of the developed transfer and
Project Analyst automations document handover
Closure
• Infrastructure • Checking and closing
Engineer financial loops

• Automation
Developers

• Client Team

UiPath Implementation Methodology Model 5

You might also like