Tag Info

Hot answers tagged

4

The deliverable is information about the system. The purpose is to help people make better decisions, based on information about the system.


2

I have worked in product development and quality assurance in three different industries. Justifying QA is an education and organizational maturity issue. The value of dedicated QA varies depending on the size of the team (specialization of roles) and the risk associated with problems in the software. Some teams cannot justify it. Every project is unique. ...


2

The problem with any form of hard metric in a field like software QA is that - to use the answer I give so often here - it depends. Each hard data point is really only helpful in the context of the development project it links to, and even then there are variations. I'd suggest you take a look at the answers to the question user867 suggested as a possible ...


1

I can think of a number of possible deliverables. Pick those that your teams and stakeholder need. I would say QA deparments provides Information/feedback about the product, e.g, bug reports test reports with test cases passing/failing, areas showing risky areas, metrics showing trends across subsequent tests, Tools to collect such feedback: ...


1

from my own experience, the deliverables can be vary from one project to another. For instance, I was involved in a very new feature that has to ship within couple of months. Due to time pressure, I wrote the deployment guide document for our sales engineers so that they will know to how to deploy in customer's environment without banging their heads against ...



Only top voted, non community-wiki answers of a minimum length are eligible