| || |
Please answer the Following Questions as soon as possible.
We are defining processes for company and we need to establish a fluent process for QA as well. We need to define QA involvement from start to end in a life time of a project. These include answering few questions:
What are industry standards?
What is the role of QA at every stage of a project (from requirement gathering to delivery/deployment)?
What is the input required from QA at every stage?
What is the out required by QA for testing at intermediate stages till the end?
What are those intermediate stages (depending upon the nature of a project)?
What documents should be developed by the team (software engineers/ managers) to be used by QA?
Format of those documents?
Method to transfer subjected project from developers to QA for testing and vise versa?
Final approval method from QA?
These are just few points to start with for the upcoming projects.
As for the immediate action point when our projects are in the middle or close to completion, please define what could be a smooth process of handing over a project to QA (along with required docs), expected response with expected time, developers first response to an error report and how we can reduce cross communication or back n forth movement of project.
Wow, that's asking quite a lot from SQAForums members!
Originally Posted by Sanazafar
You are defining a process for your company, but you are asking questions here that can only be answered by people with in-depth knowledge of your company. The answer to every one of those questions depends on
- the expectations of your stakeholders
- the specific role of QA/Testing within your organization
- the relationship of QA/Testing to other groups like Development, Produce Management, Project Management, etc
- the industry in which your company operates
- etc, etc.
Someone with knowledge of your company simply has to do the hard work. You could hire a consultant to come into your company, spend a fair amount of time analyzing, then propose a QA process, but you simply cannot get a good answer to your questions by just asking other, unfamiliar parties.
If instead you just want to see examples of how others have answered your questions, a few quick search with Google or such will turn up many, many results. But each of these results either has no real meaning (there's no "industry standard" way of answering your questions), or has meaning within a specific company which may or may not apply in yours.
Dig in, and do some work on your own. You may wish to do some searches first. And you may wish to read a few books on the topic. Here are a few: http://www.allthingsquality.com/2011...d-quality.html
Then, once you and your team have some idea of what you are really planning to do, come back and ask more specific questions.
Either that, or just pay someone to do the real work for you.
As far as I can tell, those are your only two options which will get the results you are after.