Comprehensive software reviews to make better IT decisions
Appian Is Now in the RPA Game With Its Latest Acquisition
Robotic process automation (RPA) entered the industry by storm and has caught the attention of many organizations who are looking for ways to optimize manual business processes and ease the pressure on constrained IT teams. See our Automate Work Faster and More Easily With Robotic Process Automation blueprint for more information on RPA.
Appian, a prominent player in the low-code development space, announced the acquisition of Novayre Solutions SL, developer of the Jidoka RPA platform, early in 2020. This acquisition bolsters its image as a viable vendor to empower the business with development capabilities. Appian is hoping to use this acquisition to overcome the many challenges impeding the scaling of RPA adoption and to offer customers solutions:
- A one-stop shop for automation by unifying its low-code development platform with RPA.
- The ability to centrally manage and govern the implementation and operations of RPA bots.
- Delivery of enterprise-grade RPA bots that can extend RPA use cases and management, allow more sophisticated bot development, support AI, and have SOC 2 and ISO 27001 certification compliance built in.
The recent Appian acquisition demonstrates the value RPA can bring to the industry, despite the technology and its implementation still being new. Much like any other acquisition, Appian customers will have to wait to see how the new pieces of technology will be integrated within the Appian portfolio and how Appian’s licensing model will reflect the unique licensing model that is commonly in place among RPA vendors. Only time will tell.
Want to Know More?
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.
RPA projects fail more often than one would expect. 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.
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.