Answer.

The business analyst plays a crucial role in the product or solution testing phase. Their task is to ensure that the implemented solution meets the business requirements and that the project goals are achieved. To do this, they:

1. Prepare acceptance criteria: Usually, during the requirements phase, the analyst formulates the acceptance criteria, which are later used in the creation of test cases.
2. Participate in UAT (User Acceptance Testing): The business analyst takes part in meetings, helps users and testers understand what should work and how, and gathers feedback.
3. Record defects and discrepancies: They promptly inform the team of errors identified during testing.
4. Maintain communication between the testing team, developers, and the business client: They act as a translator between the business and technical specialists.

Key features:

• Formulation of acceptance criteria at early stages
• Direct involvement in testing and verification
• Focus on business value, not just technical aspects

Tricky Questions.

Is a business analyst obliged to create all test cases independently?

No, test cases are usually written by the QA team, while the analyst formulates acceptance criteria and helps break them down.

Can the analyst completely leave the project after handing over the requirements to developers?

No, their participation is necessary until the very end to ensure that the solution meets business expectations.

Should the analyst adjust requirements after testing?

Yes, if issues or misunderstandings are identified during testing, the requirements should be clarified and documented.

Common Mistakes and Anti-Patterns

• Lack of BA involvement in testing, leading to discrepancies between business expectations and the final product
• Absence of pre-defined acceptance criteria
• Insufficient communication with QA or the business

Example from Life

Negative Case: The analyst handed over the assignment to the developers, did not participate in testing, and the requirements were incomplete. Pros: Quick completion of "paperwork" Cons: The solution did not address the business problem, requiring significant adjustments.

Positive Case: The business analyst attended the tests, prioritized acceptance criteria, and promptly clarified the requirements. Pros: Minimization of misunderstandings, alignment of the solution with business expectations. Cons: More involvement of the BA during the acceptance testing phase.