"We've shifted left."
Translation, nine times out of ten: we made the testers redundant and added "quality" to the developers' to-do list, somewhere below "ship the feature by Friday."
"Shift left" has gone from a genuinely good idea to a polite cover story for testing on the cheap. The principle is sound. The execution is often cost-cutting in a lanyard.
Shifting left means quality moves upstream: into design, into how you build, into fast feedback. It does not mean taking everything testers used to do and dropping it on engineers who are already flat out, then acting surprised when the testing that happens is a hopeful click-through at 4:55 on a Friday.
Lisa Crispin and Janet Gregory have made the same point for years: quality is a whole-team property, not a parcel you re-address to a different desk. Shift-left done badly does not make quality everyone's job. It makes it nobody's, like a group dinner where the bill lands and everyone suddenly needs the loo.
Shifting left properly looks like this:
- Testers in the room when the thing is designed, not handed the wreckage afterwards and asked to verify it floats.
- Developers given real testing skill and the time to use it, not just the responsibility and a stern email.
- Fast feedback that catches problems in minutes, not a regression suite that reports back sometime on Tuesday.
- Someone still owning the testing craft, because "everyone tests" quietly tends to mean nobody does it well.
Done right, it is the best thing to happen to quality in a decade. Done as a redundancy exercise with a fashionable name, it moves the bugs somewhere no one is looking.
into your process?
A QA Review finds the gaps in 1–2 weeks. From £1,200.