Introduction to Shift Left

[David Moss] Hi, my name is David Moss, and I’m a Senior Consultant at QA Consultants in Toronto. Today, I’d like to take a few minutes to discuss the concept of “Shift Left.”

What is Shift Left?

Shift Left is an approach to bringing testing earlier in the software development life-cycle, shifting testing responsibilities to the left of the project timeline. It reflects the maxim, “test often and test early.”

How Can Testing Be Done Before Code Exists?

At the beginning of a project, there’s no application to test yet. QA plays a role through requirements reviews and design reviews, helping identify not just system defects but also gaps in requirements and design issues.

The Value of Early Reviews

The earlier defects are found, the better the project outcomes are in terms of schedule, costs, and product quality. Senior testers and developers, along with BAs, participate in these reviews to ensure alignment with business needs and test readiness.

An Example from Experience

In a previous role with a banking client, I identified issues with vague terminology in business requirements, like words such as “would,” “should,” and “could,” which could lead to misinterpretation. Collaborative reviews helped align understanding and resolve these issues early.

Benefits of Shift Left

Early knowledge of the application improves planning, effort estimation, and staffing. As we engage in requirements and design, we can begin activities like test case design and environment setup in parallel with development.

Advice to Clients

My message to clients is to involve the test team early. Early collaboration with the BA, developers, and project managers helps ensure quality delivery on time and on budget.