Session
Shift Left Isn’t a Tooling Problem. It’s a Collaboration Debt Problem.
Shift-left is often framed just as Testing Early. Add API tests. Integrate automation into CI. Run checks earlier. Increase coverage.
But in many teams, the only thing that truly shifts is the timeline.
In one team I worked with, QA was invited into requirement analysis and sprint planning earlier than usual. During that discussion, we noticed the feature being designed already existed in another module and could be reused. That single observation saved four days of development effort. Similarly in one session, we identified edge cases that would likely have caused rework later. If those were discovered during testing, it would have meant additional QA–dev churn, retesting, and delay.
Nothing about that outcome required new tools.
It required shared visibility and shared authority.
Over time, I’ve seen a recurring pattern across teams scaling automation and CI adoption. We introduce more checks to reduce risk. We expand layers to gain confidence. But testers are still often invited after core design decisions are made. Devs optimise for their module. QA is expected to “own quality” without influencing the decisions that define it.
We call QA gatekeepers. Then we place them behind the gate.
As per my experience, We should be on a watchtower view, because testers often see system-wide impact before issues materialise. But without involvement in early conversations, that visibility turns into reactive validation instead of preventive design input.
This talk explores:
- Why many shift-left initiatives fail even when tooling is strong
- How collaboration debt accumulates across sprints and teams
- Why automation sometimes compensates for missing conversations rather than solving root causes
- How to rethink ownership, authority, and involvement when scaling quality
This is not a tooling session. It is a reflection on system design, responsibility, and how experienced testers can move from late validation to early influence.
Intended audience:Testers, SDETs, and QA leads who have implemented shift-left practices and still feel that something fundamental has not changed.
The goal is not to criticise shift-left, but to examine what actually needs to shift if we want shared responsibility instead of earlier isolation.
Manish Saini
Advocating for Smarter, Scalable, and Automation-Driven Testing | Developer Advocate 🥑 | Speaker | Mentor | Author | AI & Automation Evangelist | YT - @TechUnfilteredWithManish
Noida, India
Links
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top