Many questions arise whenever adopting exploratory testing (ET), primarily due to misunderstandings about what it means. The fact that exploratory testing is mainly unstructured, especially compared to the traditional scripted testing approach that is highly detailed and restrictive, makes it harder to connect it to the word “plan.” Sometimes, users call it ad hoc. Does all this mean that we can’t prepare ourselves for exploratory testing and establish some level of plan for it?

Success. We all seek it. However, what defines success? It all depends on the goals we have established. We often hear that testing is about ensuring there are no bugs. That's wrong in many ways. First, testing doesn't assure; testing gives information about quality so the team can decide what to do next, hopefully using it to improve its current status.