Comprehensive software reviews to make better IT decisions
RPA: Look Before You Leap
RPA projects fail more often than one would expect. In fact, a report from EY found 30% to 50% of initial RPA projects failed. The ease with which RPA tools allow workflows to get designed and implemented makes it easy to avoid building a strong foundation for the work being done.
Organizations using RPA might end up trudging along the same path
I get it. RPA tools are easy to use. They have interactive workflows and drag-and-drop widgets. Playing around with these features to spin up the next flagship product for your company is a wildly charming idea, but (and there is always a but just when the sky seems to be the limit) don’t let your eagerness push planning to the wayside.
Planning? In the age of Agile?
Agile doesn’t ask you to skydive without checking that your parachute will deploy. Similarly, trying to push your RPA solutions without having done some preplanning can lead to failure. Rather, establish a minimal prework checklist that must satisfy a criterion for quality.
A basic set of checks before embarking on an RPA implementation would include:
- Brainstorming what needs to be done. Include as many of the impacted stakeholders as you can. Don’t ignore security, privacy, data management, and other important considerations.
- Identifying processes to automate.
- What’s repetitive?
- What consumes a lot of people’s time?
- Which ones produce a net loss (or negative value)?
- Going through lessons learned from previous automation exercises.
- Documenting the effect of automation on existing resources.
- Discussing the possibility of setting up a workshop for ideation, cost-benefit analysis, teaching RPA to those who are still untrained, and understanding changes to daily work.
Is RPA a one-size-fits-all solution? What processes should we automate?
No, it’s not. Not everything that can be automated should be automated. Before deciding which processes to automate, it’s important to analyze your business and operations ecosystem. Take a holistic view of the value-generating procedural workflows, including existing legacy processes that may not be automated but may still be impacted by bots.
In general, processes that fall into any of the categories below are viable candidates for automation:
- Repetitive processes that change rarely
- Processes that are used more frequently
- Rules-based processes that can be converted into workflows
- Processes that require a high level of consistency, like data entry, data validation, etc.
- Clearly defined processes
- High-volume processes
- Data migration processes where different teams exchange data on a continual basis
Adapting your organization for RPA is like any other important project you will undertake. Without getting mired in tedious planning activities, some groundwork still needs to be completed for success to be a certainty.
RPA platforms like Blue Prism, Automation Anywhere, UIPath, and Microsoft Automate are generally well-developed tools, and failed RPA projects are likely due to lack of preparedness rather than any deficiency in the tools.
Want to know more?
Connect with one of our analysts to understand how your organization can benefit from:
- Robotic process automation
- Low-code/No-code development
Thor, the Norse God of Thunder, tells Jane Foster, the woman he’s trying to impress, that on his home world of Asgard, the realm eternal, science and magic are two sides of the same coin. Had Jane been a part of the operations teams at Google (or other mature online service providers), she would have immediately realized we have a similar technology right here on good old Earth. We call the science site reliability engineering (SRE), and service level objectives (SLO) is the magic behind it. SRE is a powerful concept for organizations that are serious about keeping their customers happy. It is therefore important for them to develop well-thought-out SLOs and make certain that management is intellectually equipped to derive valuable business perspectives from them.
Hell hath no fury like a customer not being able to access an online service when they want to. They expect the online services to always be on, always be accessible, and always treat them like there’s no one else in the world who matters more. Thank heavens then for giving these online services the ability to use site reliability engineering (SRE) to keep their customers happy, engaged, and most importantly, feeling valued.
Info-Tech members moving to Agile are frequently unsure of the role of PMs and the PMO in an Agile environment. Any organization used to traditional (Waterfall) project management will need to make adjustments in support of Agile or risk losing the benefits.
GitHub has announced that, effective April 14, 2020, all of its core features will be free for everyone. This will include private development within organizations that have previously paid for some subscription plans.
Many Info-Tech members are wrestling with how to best manage their software development productivity while working from home, especially for teams using a Waterfall approach. Sprinkling some Agile practices into their normal routine could improve transparency and show continuous value delivery.
When deciding on how to license your products or components, you don’t start with debating open vs. closed source code. It starts with asking simple questions around your overall goals.
Not all metrics are good and using poor metrics can have a serious negative impact on your organization. Maximize the value of your software development lifecycle (SDLC) metrics by using this thoughtful and judicious approach to ranking and selecting them.
We live in a metrics-fixated world where having more metrics is always thought to be better than having less, and Software Development Life Cycle (SDLC) metrics are no exception. But the truth is that any badly chosen or managed metric will do more harm than good to your organization. To avoid these pitfalls, take ownership for SDLC metrics away from managers and put it into the hands of those who can best manage it: your development teams.
Robotic process automation (RPA) success is dependent on the right business processes to automate. Blueprint helps identify the right places to apply RPA with its Enterprise Automation Suite.