Hi @eman, shifting left or right means going beyond the traditional “testing phase” in the work cycle to contribute as tester. Imagine a waterfall diagram:
analysis — design — development — testing — deployment into production — operations/support
On the left, it can include pairing with developers and participating in events like three amigos, where the PO/analyst, the developer and the tester discuss a user story or requirement to catch questions and problems early and get a common understanding of what needs to be done.
On the right, it can include working together with support personnel or using monitoring of the production deployment to guide risk analysis and testing decisions.
Especially in a continuous delivery context but also in more traditional settings it’s helpful to look beyond the edge of the own plate to look for a solid foundation for these decisions - and it doesn’t get much more solid than looking what actually happens in live usage of your software.
I hope this helps