Can we stop the nonsense of Shift Left?

by Jeremy Berriault | Sep 10, 2019

The Origin of “Shift Left” in Software Testing

Back in 2001, Larry Smith introduced the term “Shift Left,” urging test teams to get involved earlier in the Software Delivery Life Cycle (SDLC). The logic was simple: catch errors sooner, fix them for less, and deliver smoother releases.

The Real Cost of Late-Stage Defects

There’s no shortage of articles and books explaining how expensive it gets to fix issues as they move closer to production. Once a bug hits production, costs skyrocket—more people get involved, and sometimes even senior management is called in if clients are impacted.
So, the earlier you find a problem, the cheaper it is to fix. Seems obvious, right?

The Cost Myth: Are We Really Saving That Much?

Here’s something to consider: most team members are salaried, and the company is paying for their time regardless. Yes, production issues are disruptive and may cause delays, but no extra staff are typically brought in to resolve them. Meetings can be shuffled, and updates sent out, but ultimately, the same people are involved. As Capers Jones documented, those end-of-line costs are inevitable—so maybe we need a different approach.

Quality Isn’t Just a “Test Team” Issue

This is crucial: quality is not the sole responsibility of the Test team. Why should one group carry the weight? Imagine winning the Stanley Cup with only the goalie on the ice. Sounds ridiculous, right? Expecting a single team to guarantee quality is just as unrealistic.

Early Involvement: It’s a Team Sport

The “Shift Left” mindset predates 2001, but the term put the spotlight on getting Test teams involved earlier. The problem? It still singles them out. Real quality comes when everyone—developers, business analysts, product owners, and yes, testers—gets involved early and often. This aligns perfectly with the Agile Manifesto’s focus on communication and teamwork.

Beyond Shift Left: Knowledge Sharing & Root Cause Analysis

Knowledge Sharing: Fuel for Innovation

When organizations prioritize knowledge sharing, productivity and innovation soar. The bonus? Happier, more engaged employees.

Root Cause Analysis: Learning from Mistakes

A robust RCA process digs into where things went wrong and helps decide if a fix is needed. Cost alone doesn’t tell the whole story—combine it with other metrics, and you get real insight for continuous improvement.

The Bottom Line: Quality is a Team Effort

Let’s move beyond “Shift Left” as just a testing initiative. True quality happens when everyone is involved from the start, sharing knowledge and learning from every mistake.

Ready to Build a True Quality Culture?

Stop putting all the pressure on your Test team. Let’s create an environment where quality is everyone’s job—and your whole team thrives.
Book a call with Berriault & Associates today to start building a collaborative, high-performing team.