Introduction
In an Agile world, software and IT teams are under constant pressure to move faster.
Typically, this means decreasing the relative length of delivery time while continuing to improve quality on each successive release.
At the same time, there’s always pressure to minimize testing costs.
Many organizations who have adopted agile development initiatives have focused on shortening sprints and incorporating customer feedback into features faster.
But soon they run into severe quality issues, and their customers end up suffering.
An emphasis on testing and quality has made a huge emergence in the software market, where “move fast and break things” is no longer viable. A quality assurance movement known as “shift-left testing” has come along in response to this mantra.
This e-book will cover 1) why you won’t survive if you don’t shift, 2) how your testing processes should change when you adopt a shift-left testing methodology, 3) who needs to be involved in this movement and how, and lastly, 4) we’ll hear from individuals about how they pioneered the shift in their teams.
