BA-201 · Question #177
Cloud Kicks has moved into the quality assurance (QA) phase of Salesforce product configuration and extension. The QA team is now trying to confirm it has delivered value to stakeholders based on busi
The correct answer is C. Acceptance criteria. Acceptance criteria are predefined, specific, and testable conditions that a solution must satisfy to be accepted by the stakeholder. They directly answer both QA questions: 'Did we build the right product?' (the acceptance criteria trace back to the original business requirement
Question
Cloud Kicks has moved into the quality assurance (QA) phase of Salesforce product configuration and extension. The QA team is now trying to confirm it has delivered value to stakeholders based on business requirements. The team is asking questions such as, "Did we build the right product?'' and "Did we build the product right?" Which element should the business analyst use to help the QA team validate that the product fulfilled the requirements without ambiguity?
Options
- AProcess maps
- BUser stories
- CAcceptance criteria
How the community answered
(51 responses)- A6% (3)
- B10% (5)
- C84% (43)
Explanation
Acceptance criteria are predefined, specific, and testable conditions that a solution must satisfy to be accepted by the stakeholder. They directly answer both QA questions: 'Did we build the right product?' (the acceptance criteria trace back to the original business requirement) and 'Did we build the product right?' (each criterion provides a measurable pass/fail condition). Unlike process maps (which document workflows) or user stories (which capture intent from a user perspective), acceptance criteria remove ambiguity by defining exactly what 'done' looks like, making them the essential tool for QA validation.
Topics
Community Discussion
No community discussion yet for this question.