Automation

Implementation
Methodology
The Implementation Methodology Model
This handout lists the key people and tasks involved in each phase of the implementation
model.
 Stage Role Involved Key Task Output

• Solution • Set up the overall • Reviewing the

Architect expectations of the project SOW

• Project • Early RPA readiness • Setting up

Manager discussions about: communication
cadence
Kickoff • Infrastructure − Client’s environment
Engineer and infrastructure • Completing the
customer readiness
− Test and dev checklist
environments
• Initiating the Issue
− Test data/test cases Tracker

• Solution • Assess potential • Verifying the

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

• Identify the key complexity,

technical dependencies,
and access to key
applications

• Solution • Analyze the chosen • Defining and

Architect process in its as-is state finalizing the “to-be”
and start the PDD process
• Project
Manager • Identify the degree of • Completing and
Process automation approving the PDD
Analysis • Business
Analyst • Streamline the business • Creating and
flow to the ‘to-be’ process approving the UAT
plan
• Fill the PDD with the as-is
and to-be processes

The Implementation Methodology Model 2

 • Business • Design a future state flow • Completing the SDD
Analyst and maps out modules for document
automation development
• Solution • Completing the
Architect • Use Application Tracker to Application Tracker
record access required by
Solution
• Project the developer to build and • Completing the
Design Manager run automation UAT and Technical Testing Plan
Production
• Automation
Developers • Prepare the Technical
Testing plan encompassing
UAT scenarios, functional
testing, and system
integration testing

• Solution • Create the modules • Building automation

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

Development • Execute the Technical

and Testing Testing plan after
Development and Unit
Testing

• Create automated tests for

functional testing to confirm
large functions work
independently

• Complete end-to-end test

for system integration
testing

• Run all UAT test scenarios

The Implementation Methodology Model 3

 • Solution • Conduct UAT in • Executing UAT Test
Architect coordination with the Cases
implementation team
• Business • Signing off client
Analyst • Run all the potential happy- business team test
path and business execution
• Project exception scenarios
Manager • Completing the
• Ensure all agreed-upon Runbook document
• Automation scenarios are tested
Developers
• Log any deviations and fix
that with the help of the
Automation Team

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

− Production
environments

− Operating instructions
for automation

− Instructions to the
operations, IT, and
automation
implementation team

• Document the Runbook

template for every
automation

• Solution • Migrate the final process • Revising the Runbook

Architect packages, libraries, and document
assets to the production
• Project Orchestrator • Completing production
Manager bug fixes
• Identify and address issues
Deployment
and Hypercare • Automation quickly using hypercare
Developers
• Run and review production
cases using hypercare

• Fix issues promptly and re-

push to production

The Implementation Methodology Model 4

 • Initiate knowledge transfer
during hypercare

• Solution • Confirm conformance of all • Checking and

Architect services are made as per signing off contract
the contract completion by the
• Project client
Manager • Carry out the handover
process for long-term • Initiating knowledge
Project • Business support of the developed transfer and
Closure Analyst automations document handover

• Automation • Check and close financial

Developers loops

• Business
Team

The Implementation Methodology Model 5