<< HOME

SPEAKERS

AGENDA >>

GERIE OWEN - Lead Quality Engineer, ZS

ENABLING DIGITAL TRANSFORMATION THROUGH THE INNOVATION OF DEVOPS

When organizations embark on digital transformation initiatives, they often turn to DevOps because the pillars of digital transformation and the practices of DevOps are closely aligned. One of the most important benefits of DevOps brings to digital transformation is the mindset of intersectional innovation.

Intersectional innovation combines different and sometimes disparate ideas. DevOps brings together different skillsets to facilitate the continuous integration process which enables intersectional innovation.

In this presentation, we’ll discuss the role of DevOps in digital transformation. We’ll provide an understanding of how DevOps practices enable digital transformations. We’ll show how DevOps teams with seemingly disparate skills and experiences can create the intersectional innovation that is so critical to digital transformation.

AMITAI ROMANELLI - Sr. SDET, Ware2Go

RUNNING AUTOMATION IN CIRCLE

In today's complex tech stacks using infrastructure as code. We can leverage our test automation skills beyond only our product, we can use them to bring value to the DevOps team and help ensure the quality of our infrastructure as well as our product.

Follow our iterative journey from a humble set of smoke tests to a leveraged solution used by DevOps to monitor our infrastructure.

ELIZABETH STEWART - Sr. Manager, QA and Delivery, AccuWeather, Inc.

TEST ARCHITECTURE - QUALITY COLLABORATION IN A DISTRIBUTED ORGANIZATION

Implementations often span across multiple companies. How a test architect can drive better results for customer experience and integrate test architecture to achieve quality collaboration in a distributed organization.

ANNIE GARDNER - Quality Automation Engineering Lead, Deluxe

CHANGING THE TESTING MINDSET TO SHIFT LEFT

In the beginning, software development followed a waterfall methodology. While the interactions between the teams could still be respectful and open, the testers were getting involved so late in the software development process, that there was always a sense of disconnect. This disconnect could result in multiple issues. Three such examples:

A lack of understanding of the expectations or changes that have been made.

Bugs being found that cause the Developer to have to context switch from a task they are currently working on.

Releases are getting delayed due to critical bugs being found too late in the release stages.

Taking a traditional developer/quality team and asking them to change how they interact during the release cycle can be challenging. So the question becomes, how do you begin the Shift Left mindset while retaining your development and quality teams and not increasing the risk for a deliverable product? Today, we will go over some of the changes a team made in an attempt to implement Shift Left testing. What worked, what failed, and how they adapted. Some of the questions the team had to ask themselves, and how they addressed potential problems. What is the difference between quality engineering and quality assurance? Why does this difference mean so much to this shift? Where and how do the interactions begin, and how often during the course of product development? Team cohesion plays an essential role in Shifting the Left and can kill this initiative if it does not exist.

<< HOME
AGENDA >>