ROM: Delivery Methodology Flashcards
What is the objective of foundation Delivery Methodology?
Define the optimal delivery approach and embed policies for rapid and efficient automation in a structured, controlled and repeatable manner.
- Enables RPA to be delivered in a structured, controlled and repeatable manner
- Creates re-usable, resilient and scalable assets that reduce delivery effort and long-term service costs
- Helps mitigate risk by providing early visibility of potential issues
Name the phases for delivery methodology
- Define
- Design
- Build and Test
- UAT
- Deploy
Define the Define phase
- Understand how the manual process works and what the business requires from the process
- Document the detail required to train a digital worker in PDD
- Complete Functional Requirements Questionnaire (FRQ) to capture key details around the process
- Walkthrough PDD and FRQ with process SME to validate definition
Define the Design phase
- Complete a SDD documenting the proposed solution design
- Walkthrough the new design with process SME to confirm changes in approach
- Confirm agreement and approval of the design with business
Define the Build and Test phase
- Check/test each part of the process ahead of assembly
- ‘Fail fast’ to reduce the risk of the different parts of the solution not coming together as a whole
- Test in control room, to prove an object or process works both in the diagram and at full speed
- Collaborate with the ambition to evolve into a more industrial collective, with a production-line approach to delivery
Define the 3 key points of UAT phase
UAT: User Acceptance Testing
- An RPA solution is made up of more that just BP (apps, environments, data, business rules)
- Aim of the project is for digital workers to use live apps (prod versions of the app/live data)
- UAT must be conducted by the business (business must prepare acceptance tests)
Define the Deploy phase
- Package and release the solution, together with instructions on how to deploy it into the live environment
- Create instructions on how to run the solution as part of a BAU operation (operational handbook)
- Develop a robust Service Model - running BAU should be viewed as a service provided to the business
BAU: Business as usual
What is a Design Authorithy and what is its purpose?
A Design Authority is an essential feature of the BP Delivery Methodology and its purpose is to guide the delivery team, advising on how a design should consider aspects such as security, risk and test approach.