Foundation: Delivery Methodology
Through many years of experience, Blue Prism has developed an approach to delivery that is focused on far more than software deployment. This methodology is proven to ensure implementation success beyond the first handful of processes by:
- Enabling business processes to be automated in a structured, controlled and repeatable manner
- Providing best practice that increases the potential for automation and accelerates development
- Mitigating risk by providing early visibility of potential issues
- Shortening test phases by introducing Production data earlier than traditional SDLCs
- Creating re-usable, resilient and scalable assets that reduce delivery effort and long term service costs
- Identifying the skills necessary to operational teams via a role-based training, mentoring and certification
- Offering a benefits case to encourage wider recognition and adoption of RPA across the organization
The Blue Prism delivery methodology is divided into 6 phases:
- Define - examining the AS IS manual process and defining the scope of the TO BE automation
- Design - proposing a TO BE solution design to meet the client's requirements
- Build - making the design a reality
- Test - the delivery team checking the solution they will be presenting to the client
- User Acceptance Testing - the client testing that the automation works as expected
- Deploy - going live and running the automation as BAU
Discover more about the delivery approach here.
A Design Authority (DA) is an essential feature of the Blue Prism delivery methodology. The purpose of a DA is to guide the delivery team, advising on how a solution design should consider aspects such as security, risk and test approach. And ideally the DA is involved right across the delivery cycle, ensuring standards evolve as the team matures. Initially the role could be performed by an individual expert but as the Centre of Excellence matures, the DA responsibility should be shared by a group of RPA practitioners.
Discover more about the Design Authority here.
Although there are numerous responsibilities in a delivery team, with jobs such as Developer being the more obvious ones, there are some roles that Blue Prism sees as vital to the creation of an enterprise level RPA capability.
The Head of RPA is the face and voice of Robotic Process Automation within the organization.
- Accountable to executive management
- Responsible for the RPA delivery capability and ongoing RPA service to the business
- Actively promotes the wider adoption of RPA
- Acts as internal and external escalation point for operations, IT and third parties
- Engages with business and IT change management teams
- Manages any potential resistance, including both business and technical challenges
- Appoints the ROM Architect
The ROM Architect is responsible for managing the creation of the Blue Prism delivery capability within an organization.
- Engages with senior stakeholders
- Establishes a governance and communication model
- Sets up mechanisms for demand generation and pipeline management
- Works with the Technical Architect to create an appropriate infrastructure
- Establishes change management procedures
- Helps the Head of RPA to create a team of suitably experienced, trained and accredited people
In a small team the Head of RPA may also assume the role of ROM Architect.
The role of Technical Architect is to provide a platform that integrates all technical aspects of the Blue Prism infrastructure with existing architectures, including networks, virtual environments and security frameworks.
- Designing infrastructure in accordance with recommended Blue Prism principles and conventions
- Configuring an infrastructure that is efficient, well structured, maintainable and easy to understand
- Responsible for infrastructure access and security
- Responsible for maintenance and back up
- Creating and maintaining architectural documentation
- Implementing change requirements as part of a structured change process