QA On Costumer Site - rules and guide lines

There are very specific criteria to determine when QA is needed on site , as I see it only if these criteria are met then there is a point to assigning QA to the costumer site.

1. Costumer has specific system inputs which can not be simulated in a lab.
2. Specific problems can not be simulated in the lab .
   
3. Tests did not complete prior to deployment, and costumer is willing to provide a testing environment.
   

In general as you can see I think there are very few occasions justifying QA on site , how ever since on many occasions system know how is lacking and QA is forced to travel to site . When On site the following rules should be met...

1. QA has traveled on site for a specific purpose it does not include costumer instructions/ politics on site installations etc...
2. when reporting from site QA should maintain the same guidelines directing him when reporting a bug from the lab.
1. be clear and to the point
   
2. describe a specific and exact scenario
3. provide all possible available debug information
4. describe system configuration with all necessary detail

Once these rules and guidelines are followed we are certain to make the most of the QA visit on site.

When this need actually arises