Exploratory Testing - Best Bang for the Buck Quality Initiative You Must Start!

There is a famous quote by Steve Jobs starting with “It doesn't make sense to hire smart people and then tell them what to do ...”. Yes, you should follow a workflow, have procedures, documentation, etc., but if you have Leonardo DaVinci as a designer - won't you give him some freedom to work? Yes, he should follow the style guide, but he should have some time on his own in order to be able to add more value to the product.
That's why exploratory testing is the best thing that can happen to your project - even if you don't have a "DaVinci" at your disposal. That moment when the QAs can put together their creativity and experience to break your platform in unimaginable ways - priceless as a masterpiece.

Some of the benefits you'll get:
- New bugs found
- Propositions for improvements and new features
- Narrowing down the knowledge gap between the PO and the dev team
- Interesting and diverse assignment will motivate the QAs to perform better
- Takes just a couple of hours per QA making it a perfect fit for the Agile methodology

The agenda is quite simple - what should you consider "exploratory testing" and how can you integrate it into your workflow.