The traditional view of the tester’s role is to write test cases based on requirements, and repeatedly test programmers’ code against those test cases. To be the gatekeepers of quality. To find and raise defects. To be the last line of defense against buggy software making it out to users.
Then “Agile” came along – collaborative, incremental development methods promising the rapid delivery of high quality, valuable software to customers. Agile’s rise to prominence has resulted in a need for testers (and other software development specialist roles) to radically adapt their ways of working.
This talk will present some core tenets of this adaptation. It will introduce both new and experienced “agile testers” to techniques for not only being a highly effective agile team member, but a key contributor in helping their team and organisation deliver better quality software.
We will cover topics such as:
“You can’t test quality into a product” (testing vs checks, quality assurance as a process and a mindset not a role)
“Shifting left” (avoiding mini-waterfalls and being part of a collaborative, continuous testing process)
Quality conversations using “3 amigos” / story kick-offs
Establishing shared standards of product quality (“Definition of Done”)
How to avoid quality problems caused by rapid incremental development