One of the challenges for testers in agile is – the definition of the software is not fixed. It is a moving target. In the non-agile (traditional) models, testers await the code freeze to perform extensive system testing. However, this is not really an option in the agile world. Agile makes change inevitable. There may be iterations where new features may not be developed and developers may focus on fixing bugs. Testers need to embrace change and work on testing as early as possible rather than holding off a major chunk of testing until all the requirements are firmed up and implementation is complete.
Agile testers need to make the most of available time for testing. Unlike the traditional models where testers are allotted several weeks to perform testing, in the agile world the iterations / sprints are short. Tester feedback needs to be earlier and faster. It is not enough to stick to trying to accomplish the same type of testing in a faster manner. Testers in agile need to rethink their processes and how testing is performed, to make this happen.
Agile testers need to make the most of available time for testing. Unlike the traditional models where testers are allotted several weeks to perform testing, in the agile world the iterations / sprints are short. Tester feedback needs to be earlier and faster. It is not enough to stick to trying to accomplish the same type of testing in a faster manner. Testers in agile need to rethink their processes and how testing is performed, to make this happen.
