Exploratory testing

In agile development process, testing should be agile as well. But scripting approach (having TestCase base and executing test cases) is not very agile.

So, more flexible thing is exploratory testing. If your app. is a city...
Let's describe application districts:
# Financial - Features that would appear in marketing demo or sales demo.
# Historical - Legacy code. Known error-prone code (smthn like regression testing)
# Seedy - Undocumented features, vulnerable places w/ big negative impact to user
#Tourist district - Features commonly used by novice users but not experienced ones
etc.

In each district you could follow different tours for this district.
e.g.
in financial district, you could have Money tour - test features users buy the app. for (main functions), FedEx tour - follow your input thought the app. flows
in Tourist district, you'll enjoy Supermodel tour - check UI and usability, don't dig into features

And there are some other districts and tours.... so testing process in exploratory testing is based on taking some tours.

Further reading:
Exploratory Software Testing: Tips, Tricks, Tours, and Techniques to Guide Test Design by James A. Whittaker 

p.s. Have a nice trip :)

Given by Nikita (nik)