With this AMA session we kicked off our third Ask Me Anything session as part of our Rom Essentials program. We've now compiled the key questions and answers all in one place here - but if you want to read the original thread here's a link: June 17th Ask Me Anything: Delivery Methodology
A. Design Authority is a critical role that becomes especially important when an organization decides to Federate the Delivery function across multiple groups. With multiple delivery groups in different line of businesses it is important to ensure that all groups are delivering automations to the standards and best practices that are defined for the organization. When all groups know and comply with the established standards it introduces efficiencies in consistent design practices which can lead to reduced delivery timelines and enhance maintainability of the automations. The Design Authority role is centrally located to be able to establish and ensure compliance of these standards for the proposed automation solutions. Additional information on this can be found on the Blue Prism Portal at:
A. Ensuring Re-usability of the objects allows for us to reduce future delivery times when we are able to leverage previously existing objects for future builds. In order to ensure re-usability, you want to ensure the application of Blue Prism Best Practices when designing and building the objects so that they are focused on the actions they are performing, and resilient. When we build objects that perform multiple functions(read and write) they can become very isolated to the specific process vs if you build an object that reads and writes seperately, you can use those individual actions in multiple processes for that application. You can review the Build Quality Checklist for guidelines and considerations to review your objects and processes to ensure they comply with Blue Prism Best Practices. https://portal.blueprism.com/documents/build-quality-checklistDepending on the maturity and whether the organization has a centralized vs federated vs divisional delivery model. Having exposure to what objects have been built and are available can be as simple as tracking the Objects Library on a spreadsheet such as the Business Object Library: https://portal.blueprism.com/documents/build-quality-checklist or using a Private Digital Exchange to share those items across multiple groups. The Private DX is a way for your organization to upload the assets into your own private area hosted within the Blue Prism Digital Exchange(DX) in order to share the objects that have been built so that another group within the organization is also able to access them and use them for their automation solutions. The Digital Exchange can be accessed at: Blue Prism Digital Exchange
A. Blue Prisms customers are managing their development phases with agile frameworks and practices.This means that they value:* Individual actions over processes and tools * Working software over comprehensive documentation* Customer collaboration* Responding to change over elaborate plans. Typically these values play out across the delivery lifecycle and enable our customers to reduce time to value, improve the quality of the code and reduce operational overhead. EK
A. RPA teams usually find that creating testing documentation and test plans should be conducted within the team to reduce dependency on other teams and impacting the delivery timeline. That doesn't mean the SME/Business Owners shouldn't be involved in the testing. You can get your SMEs to help create the testing documentation and doing the output checks. Ultimately the process is owned by the business so their involvement is important and they will need to happy and satisfied that the process delivered is to their requirements so they will need to be engaged in order to sign off to move the process into production. There is more information on testing on our portal, link here - Test | Blue Prism PortalEK
A. Clear and consistent communications are critical in establishing trust and awareness of what is happening and how we're progressing. Having an established cadence of providing updates to the relevant stakeholders is dependent on what will work for your organization. It should be agreed with the stakeholder on how you will share information, what information is required, and how often you will provide the information. It is always good for a stakeholder to understand what stage of the delivery process that specific automation is going through(Requirements vs Design vs Testing vs Deployment) and if there are any blockers or issues that may impact our defined delivery timeline. Your stakeholders can be your partners in ensuring the success of your program in ensuring that the relevant SME's are available, the data sets are relevant and available, and that there are no major blockers that will impact the delivery of the project or if there are blockers then what are the mitigating steps we can take. The key with a good communication strategy is to ensure that the relevant information is shared in an established manner to ensure visibility and awareness that can lead to a successful outcome.
We hope our answers help you better understand around Delivery Methodoloy:
Thank you all for the questions, and to our experts for giving up their time to answer them on the Community.If you have any further questions on the topic - please post on our Robotic Operating Model (ROM) Community where community members will be ready to help you answer your queries.Many thanks.
This content has been recommended for you based on your profile information (e.g. no. of digital workers & experience)
Please update your profile information to view recommended content