| | DECEMBER 20238CIOReviewIN MY OPINIONThe traditional approach to Quality Assurance (QA) involves testing software towards the end of the development cycle. At this point, testers provide all sorts of important feedback, but it is too late and there is little the team can feasibly do, but delay the release or potentially compromise quality over schedule.This approach can no longer keep pace with the speed of software delivery in the modern era. Instead, QA must shift left, becoming an integral part of the development process from the outset ensuring the delivery of value is not stopped or slowed, but instead be part of building the value. Consequently, a re-envisioned QA organization helps the entire team collaborate to ensure that the release does not place the business at risk, undermining the very customer experience that digital transformation is dedicated to enhancing.How does a traditional QA team transform into a Quality Engineering (QE) team that requires a cultural shift towards a more shared quality paradigm that drives a collaborative and integrated approach to software development? With this shift, the QE role is then expanded and elevated to assist teams with defining and achieving quality objectives. Here are a few key imperatives to assist with the transformational journey.By Brett Scyrkels, SVP, Director, Software Quality Assurance, BOK FinancialReorganize for scale and focusAssess the current state of the quality assurance team, its processes, and its tools. This can be done by conducting interviews, surveys, and analysis of data and reports. The goal is to identify the strengths and weaknesses of the team and areas for improvement.Define the vision for the modernized QE team. This should align with the overall business strategy and goals, and should be communicated clearly to all team members.Identify the gaps between the current state and the desired state. WHY MUST TRADITIONAL QUALITY ASSURANCE TEAMS TRANSFORM AND HOWBrett Scyrkels
< Page 7 | Page 9 >