Automation CoE at Scale Using Agile to build RPA

Automation CoE at Scale Using Agile to build RPA

• 1.
  1www.hexaware.com | ©Hexaware Technologies. All rights reserved.
• 2.
  2www.hexaware.com | ©Hexaware Technologies. All rights reserved. Agile Automation at Scale Process Discovery Process Prioritization Automation Assessment •Automation Potential •ROI / Benefits •Epics / Stories Automation Pipeline Process Definition (PDD) Solution Design (SDD) DevelopmentTesting Ready for Deployment Automation Delivery Sprint Planning Built-In Quality 2-week sprints Cross-functional Teams • Scrum Master • Product Owner • Business SMEs • Developer • Tester • Business Analyst • Architect • Enablers Best Practices • Build / Release management • Bot store (reusability) • Automation Pipeline drives Architectural Runway • KT for Digital Workforce Management and Support Architectural Runway Create RPA Awareness Demand Generation Driven by… • Executive Sponsors • Automation Champions Discovery Process Inventory Approved Opportunities Prioritized Processes Initial Discovery Ongoing Nominations Prioritization Model Approval for Automation Pipeline Who’s involved? • Department Heads • Process Owners • Process SMEs • Automation Business Analysts • Solution Architects • Enablers Key Success Factors • Understanding of process automation • Effective channels for submission of opportunities and feedback • Workflow to track progress of each opportunity and manage approvals
• 3.
  3www.hexaware.com | ©Hexaware Technologies. All rights reserved. Generating demand • What is RPA? Creating awareness about the capabilities and benefits of process automation will jumpstart demand generation and facilitate discovery of opportunities across departments and teams Leverage executive sponsorship and automation champions to evangelize RPA and create widespread awareness of process automation and its benefits • Identifying suitable use cases • Benefits of automation • Tools used to automate • Types of automation • RPA in action! (Bring a demo) • Goals & objectives of automation program • How to recommend a process for automation
• 4.
  4www.hexaware.com | ©Hexaware Technologies. All rights reserved. Generating demand Creating awareness about the capabilities and benefits of process automation will jumpstart demand generation and facilitate discovery of opportunities across departments and teams Leverage executive sponsorship and automation champions to evangelize RPA and create widespread awareness of process automation and its benefits Identifying suitable use cases What is RPA? Benefits of automation Tools used to automate Types of automation RPA in action! (Bring a demo) Goals & objectives of automation program How to recommend a process for automation
• 5.
  5www.hexaware.com | ©Hexaware Technologies. All rights reserved. Assessing opportunities and building the pipeline Process Inventory Approved Opportunities Prioritized Processes Automation Pipeline Initial Discovery • Identify initial areas of focus Build process inventory for each area of focus • Populate prioritization model and adjust weightages • Get prioritized list of processes that are candidates for automation Process Automation Opportunity Discovery Workflow Ongoing Nominations • Create medium for accepting automation requests from users • Nominated processes enter a workflow for evaluation and approval of requests • Implement a feedback mechanism for suggested opportunities Prioritization of opportunities in process inventory Prioritization approach is based on 4 main dimensions: • Process Complexity • Volume • Operational Complexity • Risk Ranking of most suitable candidates for immediate automation Identify candidates that require process improvement or standardization prior to automating Deep-dive into prioritized opportunities to validate suitability for automation and potential benefits • Process walkthrough • Step-by-step automation analysis • Design high-level solution • Calculate ROI and build business case Output from the automation assessment • Step-by-step automation analysis • Current state process maps • Future state process maps • Business case with ROI • Initial Epics/Stories with SP estimates Who’s involved? • Department Heads • Process Owners • Process SMEs • Automation Business Analysts • Solution Architects • Enablers Key Success Factors • Understanding of process automation • Effective channels for submission of opportunities and feedback • Workflow to track progress of each opportunity and manage approvals
• 6.
  6www.hexaware.com | ©Hexaware Technologies. All rights reserved. Automation Assessment Process Prioritization Process Discovery Assessing opportunities and building the pipeline Initial Discovery • Identify initial areas of focus Build process inventory for each area of focus • Populate prioritization model and adjust weightages • Get prioritized list of processes that are candidates for automation Ongoing Nominations • Create medium for accepting automation requests from users • Nominated processes enter a workflow for evaluation and approval of requests • Implement a feedback mechanism for suggested opportunities Prioritization of opportunities in process inventory Prioritization approach is based on 4 main dimensions: • Process Complexity • Volume • Operational Complexity • Risk Ranking of most suitable candidates for immediate automation Identify candidates that require process improvement or standardization prior to automating Deep-dive into prioritized opportunities to validate suitability for automation and potential benefits • Process walkthrough • Step-by-step automation analysis • Design high-level solution • Calculate ROI and build business case Output from the automation assessment • Step-by-step automation analysis • Current state process maps • Future state process maps • Business case with ROI • Initial Epics/Stories with SP estimates Process Inventory Approved Opportunities Prioritized Processes Automation Pipeline Who’s involved? • Department Heads • Process Owners • Process SMEs • Automation Business Analysts • Solution Architects • Enablers Key Success Factors • Understanding of process automation • Effective channels for submission of opportunities and feedback • Workflow to track progress of each opportunity and manage approvals Process Automation Opportunity Discovery Workflow
• 7.
  7www.hexaware.com | ©Hexaware Technologies. All rights reserved. Agile automation delivery Scrum Team Daily Scrum Product Backlog Sprint Backlog Sprint Planning Sprint Review (Bot) Increment Sprint Retrospective • Approved processes from Automation Pipeline • A process is an Epic, broken down to smaller stories • Scrum Master • Product Owner • Development Team (4 to 8 members) • Architect • Developer • Tester • Business Analyst • Potentially releasable process automation solution (bot) • Must be “Done” • Inspect and adapt • Bot increment demo to stakeholders • 2-week Sprints
• 8.
  8www.hexaware.com | ©Hexaware Technologies. All rights reserved. Agile automation delivery – keys to success The Automation Pipeline and Product Backlog must provide transparency and visibility into architectural enablement requirements for upcoming work (e.g. RPA licensing, RPA infrastructure, access to business applications, test data, etc.) Epics may be prioritized based on business value of automation for each process, while stories must maintain a logical sequence based on order of processing steps Keystroke-level process details and requirements must be captured and documented for each story during the Sprint Clear definition of “Done” Continuous Build/Release Management for Bots Effective handover to production support • Requirements and solution design documentation created and approved • Test cases, Test coverage (if applicable) • No known defects • Acceptable quality as defined by Product Owner • Approved by Product Owner Sample Definition of “Done”
• 9.
  9www.hexaware.com | ©Hexaware Technologies. All rights reserved. Agile Automation Delivery – Keys to SuccessSuccessfulAutomation Delivery The Automation Pipeline and Product Backlog must provide transparency and visibility into architectural enablement requirements for upcoming work (e.g. RPA licensing, RPA infrastructure, access to business applications, test data, etc.) Epics may be prioritized based on business value of automation for each process, while stories must maintain a logical sequence based on order of processing steps Keystroke-level process details and requirements must be captured and documented for each story during the Sprint Clear definition of “Done” Continuous Build/Release Management for Bots Effective handover to production support • Requirements and solution design documentation created and approved • Test cases, Test coverage (if applicable) • No known defects • Acceptable quality as defined by Product Owner • Approved by Product Owner Sample Definition of “Done”
• 10.
  10www.hexaware.com | ©Hexaware Technologies. All rights reserved. Phase 2: Implement CoE •Build phase 2 pilot bots across BUs •Manage Global Automation Pipeline •Build Automation Library •Employee Re-skilling strategy •RPA delivery Team Training •Operationalize CoE Automation CoE enablement Program Approach • Establishment of a scalable operating model for the deployment of Robotic Process Automation (“RPA”), by implementing an Automation CoE and Global Automation Pipeline Management • Duration: 12 weeks • Program executed in 4 workstreams: – WS 1 – RPA tool selection – WS 2 – Robotic Program Design – WS 3 – Pilot Bot development – WS 4 – Opportunity Assessment Key assessment areas within financial services:- • Title Management • Centralized and consolidated automated follow- ups for title • Lien registration and release • Account Maintenance • Periodic Reporting • Insurance follow-up • Corporate Branch Functions • Payment Reconciliation • Manual floor-planning for co-part auctions • Business Development • Overline Requests • Temporary Increase Requests Fortune 750 vehicle financial services organization About the Client Global Fortune 750 company that is into institutional vehicle auctions and Independent dealer vehicle floorplan financing Objectives • Leverage internal resources, partner capabilities and best practices to launch a global Center of Excellence Automation • Establish a Global Automation Pipeline • Generate Quick Wins targeting key automation opportunities Deliverables Phase 1: Establish CoE Organization •Identify and recommend a suitable RPA Tool •Develop a detailed program design draft. •Creating RPA CoE structure with key roles & RACI & staffing plan •Automation Assessment to identify Quick Wins & strategic roadmap for RPA deployment •CoE Standard Operating Procedures •Training on Prioritization and Assessment •Organization Change Management Plan •Create Benefit Realization Tracker •COE Launch Plan •Build Pilot Bot for 1 BU
• 11.
  11www.hexaware.com | ©Hexaware Technologies. All rights reserved. Innovative Services Passionate Employees Delighted Customers Thank you www.hexaware.com
• 12.
  12www.hexaware.com | ©Hexaware Technologies. All rights reserved. Scrum Team in the context of automation development The Product Owner • Sole person responsible for managing the Product Backlog • Works closely with process SMEs The Development Team • Architect • Developer • Tester • Business Analyst Development Team Size • 4 to 8 members The Scrum Master • Responsible for promoting and supporting Scrum • Serves the PO, Development Team and the Organization The Scrum Team delivers potentially releasable process automation solutions incrementally and iteratively based on the definition of “Done”.
• 13.
  13www.hexaware.com | ©Hexaware Technologies. All rights reserved. Scrum Events in the context of automation development The Sprint • Typically time-box of 2 weeks • Contains Planning, Daily Scrums, development work, Sprint Review, and Retrospective Sprint Planning • Time-box of 4 hours • What can be done • How will it get done • Sprint Goal Daily Scrum • Time-box of 15 min • What was done yesterday • What will be done today • Impediments to meeting the Sprint Goal Sprint Review • Time-box of 2 hours • Inspect the Increment and adapt the Product Backlog • Bot increment demo to stakeholders Sprint Retrospective • Time-box of 2 hours • Scrum team self- inspection and improvement planning for upcoming sprints All Scrum Events are applicable to automation delivery. The Sprint is the container for all other events, and all events are time-boxed.
• 14.
  14www.hexaware.com | ©Hexaware Technologies. All rights reserved. Scrum Artifacts in the context of automation development Product Backlog • Ordered list of everything that is known to be needed in the automation solution • Lists all requirements, processing steps, enhancements, and fixes that are required to automate the process • An end-to-end process may be considered an Epic that may be reduced to logical groups of steps and functionality as backlog items Sprint Backlog • Set of Product Backlog items selected for the Sprint • Plan for delivering the product Increment and realizing the Sprint Goal Increment • Sum of all the Product Backlog items completed during a Sprint plus the value of the increments of all previous Sprints • An increment may be one or more components of a bot, or a fully functional bot • An increment must be “Done” at the end of the Sprint. All Scrum Artifacts are applicable to automation delivery, and provide transparency and opportunities for inspection and adaptation.
• 15.
  15www.hexaware.com | ©Hexaware Technologies. All rights reserved. Automate Everything Cloudify Everything Transform Customer Experience To transform how IT services are delivered and to be the first IT services company in the world where half the Workforce is Digital OurStrategy Focussed Growth Aspirations Automation First DNA OurApproach Culture of Bottom Up Innovation Constantly Delighting Customers Outcomes Industry Leading Revenue Growth 607 Mn (FY 2017) Rated #1 Service Provider in Europe for last two years Disruptive Trends Require a Next Gen Focused Partner Hexaware Introduction
• 16.
  16www.hexaware.com | ©Hexaware Technologies. All rights reserved. Alliances and Partnerships with Vendors Hexaware IP to Accelerate RPA Adoption Digital Operations Command Centre Configuration Manager RoboBank Unified Screen Making it Real IA ConsultantsRPA Projects 75+ 360+ 600+ Existing Consultants Scale up by end of Dec 2019 Hexaware RPA Research Lab to enable quick time to market and faster benefit realization Delivered + In Progress Solutions • RPA • AI / ML Back Office • Virtual Assistants • Conversational Bot Front Office • Multi-channel Customer Interaction Platforms • Analytics • OCR / ICR Functionality Enablers • NLP & NLG 450+ Bots ( LIVE ) 100+ Bots (in progress) 120+ Bots (in pipeline) Hexaware’s RPA Practice Statistics Hexaware’s Automation Practice Overview
• 17.
  17www.hexaware.com | ©Hexaware Technologies. All rights reserved. HiPAS Service Offerings Maturity Level Assessment & Consulting CoE Setup/ Factory Model Develop POC’s Staff – Aug Implementation Services + Licenses Bot Management & Support Operational & Transactional Analytics Initialization: Wants to start Automation journey Intermediate: Few PoC Bots built with internal resources, but needs to scale Industrialized Automation CoE: Deployed multiple Bots but want to reduce costs Advisory Implementation Management Immediate Need Future Need