When dealing with QA yo must remember that there are extensive IT requirements, this is of course product dependent , but for true QA to exist, several things must occur which relate to IT.
First and foremost Product Manager/ System manager must define :
And here comes the tricky part who is in charge of the installation and maintenance of these environments.
In the organization in which I am part of w do not have a separate IT group. this creates havoc in my opinion for the following reason.
First and foremost Product Manager/ System manager must define :
- on which Platform the Product must run.
- What are the minimal system requirements for the product.
And here comes the tricky part who is in charge of the installation and maintenance of these environments.
In the organization in which I am part of w do not have a separate IT group. this creates havoc in my opinion for the following reason.
- Not all QA are predefined to have IT capabilities and thus a lot of time is wasted due to insufficient skills.
- Since no proper IT exists there are no predefined sets of instructions as to how and what exactly to set up with in the Platform itself
- QA time is "wasted" on OS setups.
- Since QA are not exactly qualified for this they find it difficult to issue clear instructions to system Field Engineers on how to set up costumer systems, thus creating in consistency of OS types and configuration ... which basically will lead to unexplained problems from specific costumer with out any clear reason.
- No one can handle new hardware certification/ old hardware End-Of-Life replacement.
No comments:
Post a Comment