Managed Automation - The Answer to Agile Development
April 24, 2017

Ayal Zylberman
QualiTest Group

"Nothing is sure in life except for death and taxes," the saying goes. If someone were to update that expression for present day tech consumers, they could add: "and the expectation of regular software updates." It's what developers are tasked with, and what users expect and demand – increased functionality, better performance, and fewer bugs – often in a week or less. Automation of critical processes such as QA can help meet the gargantuan task of constant updates, but it can also send your software into a death spiral of user abandonment unless deployed correctly.

How We've Attempted to Meet the Challenge of Continuous Deployment

One of the most significant developments in attempting to streamline the process of continuous deployment is agile development. Agile development is a general project management approach that emphasizes the dividing of product development work into small manageable portions. These are worked on by a cross-section of teams from those that deal with coding, to those that oversee design and testing.

By breaking tasks into manageable cross-sections, companies are well positioned to put out incremental updates that fix bugs, include new features and keep the user happy. The only issue with this is that adopting the strategy alone isn't feasible for smaller companies, and even for those companies that can afford it, paying developers for the time it takes to release at that pace can be financially draining.

Why Automation of QA Is So Promising

By turning to automation for some of the processes such as QA, companies can theoretically be working to debug and improve quality 24/7. Moreover, it saves the enormous amount of money that the large staff capable of churning out those updates would cost for the SMEs that can't afford it. For those that can, it frees up engineers' time so that they can develop even better features and utilize their time more efficiently.

Nonetheless, although automation can seem like the perfect solution, relying on it exclusively may end not with increased productivity, but rather massive product abandonment and total failure.

How to Utilize Automation Without Failing

Over 60% of automated solutions fail. This rate is startlingly high, but is also largely caused by avoidable issues. Most commonly, automation testers themselves lack the skills to provide proper implementation of automation.

People overseeing the process often use the wrong automation tools or frameworks and fail to adapt regression tests which eventually grow stale, depending on them over and over instead of making sure that they evolve with the product itself.

But it's not just those who directly oversee the automation process that are at fault; it's also more often than not the framework established by the organization that contributes to automation failure.

Automation's Place

Automation is still not a solution for every problem, nor is it possible to make each testing solution 100% automated. The most common mistakes and improvements relating to automation still rely on human QA testers. It's important to make sure that any automation process includes a pairing with experienced testers with industry-specific experience. By focusing on adding skilled employees who fit into the automation process as an add-on rather than trying to make the automation process a cure-all, companies can gain a competitive edge and make better products, faster.

The agile development process is here to stay and those who don't adapt will get trounced until they are made completely obsolete. This shock to the software development process is a challenge because it requires quick adaptation, continuous updates, and a lot of critical work done on a tight timeline.

But, it's also an opportunity that can be leveraged through a delicate balance of automation and experienced QA professionals. Getting the combination right will mean money saved, better products, and happier customers.

Ayal Zylberman is CEO and Founder of QualiTest Group.

The Latest

May 25, 2017

DevOps brings Development and Operations together with the sheer objective of ensuring quality and enabling faster time to market. However, what happens to QA in this scenario? How does the Testing team fit in? Let's ponder on this further and understand the role of QA and Testing in the DevOps world ...

May 23, 2017

When organizations adopt containers and microservice style architectures in production, systems become incredibly complex. For operations it's a shock because it means coming to grips with many new container tech nuances - plus letting go of the old monitoring rule book ...

May 22, 2017

Managing application performance today requires analytics. IT Operations Analytics (ITOA) is often used to augment or built into Application Performance Management solutions to process the massive amounts of metrics coming out of today's IT environment. But today ITOA stands at a crossroads as revolutionary technologies and capabilities are emerging to push it into new realms. So where is ITOA going next? With this question in mind, DEVOPSdigest partner site APMdigest asked experts across the industry for their opinions on the next steps for ITOA ...

May 18, 2017

In Part 3 of my Q&A with industry analysts, I ask: What trends will have the biggest impact on the software industry and DevOps in particular this year and beyond? How can enterprises set themselves up to succeed with so many rapid changes occurring in development and delivery? ...

May 16, 2017

See how to turbo-charge the impact of APIs, according to a global study conducted by CA Technologies ...

May 15, 2017

APIs are vital components for business success and thriving in the application economy, according to a global study conducted by CA Technologies ...

May 11, 2017

In Part 2, I'll dive into some findings from CollabNet's outreach to industry analysts. I asked them about the greatest challenges facing enterprises venturing into the world of DevOps and to touch on what lies ahead for the future of the DevOps movement ...

May 09, 2017

DevOps teams bring significant benefits to their organizations. Unfortunately, DevOps teams, like many business programs, tend to believe innovation must come with a detriment to security. Security measures are often seen as obstacles that impact the agility that DevOps teams rely on ...

May 08, 2017

With increased competition, enterprises now require greater agility than ever before, and traditional approaches simply can’t provide the speed enterprises demand. To remain competitive with these new players, companies need to improve their operational agility both in the data center and the WAN ...

May 04, 2017

There is no "right" culture for DevOps, but characteristics such as open communication, high cooperation, collaboration, respect, and trust are essential. If your organization does not have these characteristics, they must be developed. Culture is learned, not inherited. It must be genuinely nurtured by everyone from executive management on down the line. Here are some hacks to help develop a positive DevOps culture ...

Share this