Agile Business Analysis Acceptance Criteria and Definition of Done 2 — Questions and Answers
Question 1: What is the role of a business analyst during agile testing activities?
- Writing all automated test scripts independently
- Performing load and performance testing
- Collaborating with testers to ensure test cases align with acceptance criteria (Correct answer)
- Managing the test environment infrastructure
Correct answer: Collaborating with testers to ensure test cases align with acceptance criteria
Business analysts collaborate with testers to ensure that test cases align with acceptance criteria and that the delivered solution genuinely meets business needs.
Question 2: In Behavior-Driven Development (BDD), what is the primary benefit for business analysis?
- It eliminates the need for manual testing entirely
- It creates a shared language between business stakeholders and technical team members (Correct answer)
- It automates all regression tests without human input
- It replaces the need for written acceptance criteria
Correct answer: It creates a shared language between business stakeholders and technical team members
BDD creates a common language using Given-When-Then scenarios that bridge the communication gap between business stakeholders, testers, and developers.
Question 3: What is exploratory testing in an Agile context?
- Testing performed exclusively by automated tools
- A structured testing approach following detailed predetermined test scripts
- Simultaneous learning, test design, and execution guided by tester judgment (Correct answer)
- Testing performed only in production environments after release
Correct answer: Simultaneous learning, test design, and execution guided by tester judgment
Exploratory testing involves simultaneous learning, test design, and execution where testers use their skills and intuition to discover defects without relying on rigid predefined scripts.
Question 4: Which testing practice is most aligned with the Agile principle of early and continuous feedback?
- End-to-end testing performed at project completion
- User Acceptance Testing (UAT) conducted only at the end of a release
- Continuous integration with automated tests running after each code commit (Correct answer)
- Monthly regression testing cycles
Correct answer: Continuous integration with automated tests running after each code commit
Continuous integration with automated tests running after each commit provides immediate feedback to the team, directly supporting Agile's emphasis on fast, continuous feedback loops.
Question 5: What does 'shift left testing' mean in an Agile context?
- Moving testing tasks to the left column of the sprint board
- Involving testing activities earlier in the development process (Correct answer)
- Prioritizing lower-severity defects before high-severity ones
- Assigning all testing responsibilities exclusively to developers
Correct answer: Involving testing activities earlier in the development process
Shift left testing means involving testing activities earlier in the development lifecycle to catch defects sooner and reduce the cost and rework associated with late discovery.
Question 6: In Agile, what is the purpose of a sprint review from a quality and validation perspective?
- To review and update the formal test plan
- To demonstrate working software and gather stakeholder feedback on delivered functionality (Correct answer)
- To assign discovered bugs to specific developers for fixing
- To finalize all release documentation
Correct answer: To demonstrate working software and gather stakeholder feedback on delivered functionality
Sprint reviews demonstrate working software to stakeholders who then provide feedback, validating that delivered features actually meet expectations and business needs.
Question 7: How does Test-Driven Development (TDD) support Agile Business Analysis?
- It eliminates the need for business analysts on the delivery team
- It ensures tests are written before code, creating a clear specification from the start (Correct answer)
- It automates the creation of user stories directly from test results
- It replaces acceptance criteria with unit test outputs
Correct answer: It ensures tests are written before code, creating a clear specification from the start
TDD requires writing tests before code, which forces clarity about what the code must do and creates a specification that aligns with acceptance criteria defined during business analysis.
What is the role of a business analyst during agile testing activities?