NEW-General info about QA on the project

Here are key ideas you should keep in mind about QA on the project:

1. QA Analyst is a standard project role and it should be part of every projects team together with other roles - PM, SA, CE, IE, BA

2. QA Analyst is in general expert on software testing on the project and his main responsibility is functional testing during Feature Sprints and documenting testing based on user stories using test management tool

3. In case the customer insist on not having QA Analyst in the project team (mostly to reduce the project cost), such a decision can significantly increase the project risks

4. In case the customer need some help about testing on the project, QA Analyst is the right project role task for it

5. Pricefx is responsible for testing during Feature Sprints, the customer is responsible for UAT testing

6. There are still some myths about testing on the project, you should know about them and be prepared to discuss about them (for details see /wiki/spaces/CUST/pages/1932329897 ):

   1. bug free delivery expectations

   2. testing is expensive

   3. developers can test, we don’t need a new role in the project team

   4. manual testing is not necessary, test automation will solve everything

   5. testing after upgrades is not necessary