1. Introduction
    1. Dev ; tester ; program Manager pound on the Product, each exercises the product in every way they can think of
    2. Each Person will use app differently , with different perspective
    3. In short amount of time this approach reveals many bugs relatively quickly
  2. Objective of the initiative
    1. To get together a mixed role team and get into the shoes of testers
    2. Test the application as per Release features and its impact on the complete application
    3. Go adhoc and do exploratory testing and find as many defects as we can.
  3. Benefit from the Activity to ESM Application:
    1. It will help in bringing in new perspective to testing.
    2. Bug bash will bring in a fresh pair of eyes who would use the application in an unconventional ways.
    3. It is similar to Basic usability and acceptance testing of the application used by different role people.
    4. It helps in pounding the system from a load as well as test focus perspective.
    5. It can generate a whole new set of suggestions for either enhancing the feature set, or tweaking them to make the application more valuable.
  4. How to do Bug Bash for ESM Project :
    1. Declare a time slot of 1-2 hours for bug bash in advance
    2. Compose a team of good mix ( PO ; PGM ; Dev Leads ; QA Lead ; QA Team)
    3. Small brief for the session and features to be tested as per different roles
    4. Let all the testers pound the system for 1-2 hours.
      1. Do not peer over their shoulders to guide them, or correct them.
    5. Have the coordinator team make a record of the issues faced and any suggestions or enhancements shared by the testers
    6. At the end of the exercise Bug Bash Team can consolidate all the issues and suggestions and summarize them for the team.
    7. Filter out the known issues and suggestions / enhancements that are not warranted from this list.
    8. Now what you are left with will probably be a good number of never encountered / tested defects, and suggestions and enhancement that will improve the software further.
    9. Roles for the Team
      1. Co-Ordinator
      2. Tester
      3. DB and Error Log Analyst
      4. Bug Bash Team
  5. Award/Recognition
    1. Maximum bugs added for Each Release by tester would be recognized via Star Points