Shifting Left: It's Not Just about Testing Earlier

The agile landscape is always evolving. One of the newest trends is the "shift left" approach, where testing is performed as early and as often as possible in the project lifecycle. If done correctly, shifting left enables teams to highlight poor design, provide quicker feedback to development, review progress sooner, and provide quicker turnaround on customer feedback. Unfortunately, many teams lack the discipline, time, or strategy to actually get out of their current rhythm and shift left. As testers, we yearn for the ability to test early with confidence, so we have time at the end of the sprint to perform exploratory testing or finish our automation. But how can we do this if we can't properly shift left? Join Matthew Weinstock as he shares his experiences in shifting left from a tester's point of view. We'll explore what it truly means to shift left (and right) and what concepts you can add to your toolbox to reduce testing without sacrificing quality. Learn what underutilized agile practices can help with team ownership of quality, and how you can use your fellow team members to shorten your testing cycles (without having them formally test).