Exploratory Testing is considered as the most powerful and skilled approach in testing. Though, it is accepted as the most effective approach by most of the people, yet, it is not 'formally' implemented in engagements/projects of many off-shore companies due to various factors.
Why should I do exploratory testing?
My client does not ask for it.
How do I report the accountability in Exploratory Testing?
What about coverage in Exploratory Testing?

- Probably, these are some of the reasons for not practicing Exploratory Testing 'formally'.

James Bach mentioned in Oredev 2008 that more and more people talk about exploratory testing nowadays with some of them understanding it actually.

In this experience report, I have tried to show case how I implemented the learning & skills of exploratory testing in my team with great results which eventually resulted in Exploratory Testing to be formally accepted as part of our test execution. Also, we addressed the accountability and coverage factors for our demanding Client. For us the Exploratory Testing proved to be a 'steroid' of testing - Recognition from management.

Also, I have tried to write how the experiences and lessons of several test experts proved to be true when I started practicing exploratory testing.

Shaham is an engineering graduate and has total three and half years of diverse work experience with one and half years in Software Testing and two years in financial sector. He has contributed significantly in implementing exploratory testing in his present client engagement. Shaham is alumni of Edista Testing Institute and a regular member of AST (Association of Software Testing). He is also a BBST Graduate.