With the rise of DevOps, will QA lose its identity while being merged with pluri-disciplinary cohorts, or will it survive the revolution, becoming stronger and more essential? These along with several other topics were at the center of discussions at the 2017 QA Financial Forum in New York last week.
Key takeaways from the event include:
Pressure is mounting for organizations to modernize heavy legacy systems, and that has largely pushed them toward DevOps, Agile and cloud migrations, among other IT modernization initiatives.
To further these modernization goals, many fintechs and modern insurers have merged QA roles with developers, production testers and DevOps experts to re-enforce structural quality gates. This has caused a significant percentage of the QA community to blend into these other roles.
In more traditional companies, however, the fate of QA is not as straightforward. Within these organizations, the QA function is more centralized, sometimes even divisionally decentralized, but always independent from the development organization. Here, QA teams have been continuously improving automation techniques, improving compliance with ever-changing regulations and ensuring software security.
Some CIOs have gone as far as to completely segregate application development from application support and maintenance, with application development teams clearly focused on DevOps and releasing apps more quickly, while application support and maintenance remains focused on software performance and maintaining complex quality issues with heavy support from QA.
As speakers discussed the current environment at the QA Financial Forum, additional trends emerged: