Page Comparison

Full time allocation

(this should correspond to expected 1:2 ratio (1 QA Analyst for 2 CEs on the project))

Pilot / New projects, full QA support for the customer is expected

• stand-up meetings

• UAT intro with the customer

• SA, CE discussions - scope and solutions

• Integration and data testing

• document integration and data testing

• X-Ray preparation

• test plan and test strategy preparation

• stand-up meetings

• SA, CE discussions - user stories and AC discussions

• create test cases

• X-Ray usage

• testing according to test cases - positive cases

• testing according to test cases - negative cases, exceptions

• report bugs as sub-tasks

• Pfx project team communication

• communication with the customer about UAT preparation and testing related issues

• investigate bugs from customer

• sw demo for the customer (prepare and deliver)

• regression testing after bugfixes

• smoke testing before customer testing

• SPOC for the customer for all QA related issues

• stand-up meetings

• SPOC for the customer for all QA related issues

• Customer support (UAT testing)

• Smoke testing

• bug investigation and retesting

Half time allocation

(this should correspond to about 35% - 40% of CE allocation for QA Analyst)

Pilot / New projects, basic QA support for the customer is expected

Risk: As we don’t expect using X-Ray in this option, it can be difficult to share our test cases with the customer. The customer can get some examples, but he should know our support in this will be limited.

• stand-up meetings

• UAT intro with the customer

• Integration and data testing

• test plan and test strategy preparation

• stand-up meetings

• create test cases (no X-Ray usage expected)

• testing according to test cases - positive cases

• testing according to test cases - negative cases, exceptions

• report bugs as sub-tasks

• Pfx project team communication

• communication with the customer about UAT preparation and testing related issues

• regression testing after bugfixes

• smoke testing before customer testing

• stand-up meetings

• Smoke testing

• bug investigation and retesting for internal team

12 hours a week

(this should correspond to about 25% of CE allocation for QA Analyst)

Smaller project, QA Analyst will support internal Pfx team only, NO SUPPORT FOR THE CUSTOMER

Risk: if the customer maturity in testing is low, without QA Analyst support it can lead to not prepared UAT tests, misunderstandings reported as bugs and project delay.

• stand-up meetings

• basic integration and data testing

• high-level test strategy preparation

• stand-up meetings

• create test cases (just high level, to be used by internal team only)

• testing according to test cases - positive cases

• report bugs as sub-tasks

• Pfx project team communication

• regression testing after bugfixes - partly

• stand-up meetings

• bug investigation and retesting for internal team

8 hours a week

(this should correspond to about 20% of CE allocation for QA Analyst)

Smaller project, QA Analyst will support internal Pfx team only, NO SUPPORT FOR THE CUSTOMER

Risk: if the customer maturity in testing is low, without QA Analyst support it can lead to not prepared UAT tests, misunderstandings reported as bugs and project delay.

• stand-up meetings

• high-level test strategy preparation

• stand-up meetings (partially)

• testing according to user stories - positive tests only

• report bugs as sub-tasks

• Pfx project team communication

• bug investigation and retesting for internal team

4 hours a week - note this can be used just for next stage of existing project when QA Analyst was on the previous stage and therefore knows the project and the customer. DON’T USE THIS ALLOCATION FOR A NEW PROJECT!!!

Existing customer, ongoing project, small enhancements, no support to the customer

Risk: For a new customer this option has no sense, it means NO QA Analyst on the project with all consequences as here there will be no QA support for the customer and for our internal Pfx team

• for the next stage of an existing project, QA Analyst can do basic exploratory testing with very limited documentation