Sometimes, test teams may be perplexed about how to switch to agile. If you work on such a team, you almost certainly have manual regression tests, both because you’ve never had the time to automate them or because you test from the UI, and it does not make logical sense to automate them. You most likely have excellent exploratory testers who can uncover defects within complicated systems, but they do not automate their testing and require a finished product before they begin testing. You understand how to schedule testing for a release, but everything must be completed within a two-, three- or four-week iteration. How do you pull it off? How do you stay up with technological advancements?
This is a persistent challenge. In many businesses, developers believe they have moved to agile, but testers remain buried in manual testing and cannot “stay current” after each iteration. When I communicate to these professionals that they are only experiencing a portion of the benefits of their agile transformation, developers and testers say that the testers are too sluggish.