Objective: Writing Acceptance Criteria CT-ACT Practice Questions (Page 5)

Questions 21–23

1. 21application · medium

   A product owner writes: 'The system must allow users to reset their password.' The team is about to start development. Which action best improves this statement into a usable acceptance criterion?

   • AAdd a note that the feature must be 'user-friendly' and 'secure' so developers know the quality bar.
   • BState that the feature must work 'for all users' to ensure completeness.
   • CRewrite it as: 'Given a registered user on the login page, when they select "Forgot password" and submit a valid email, then a reset link is sent to that email within 2 minutes.'
   • DCreate a detailed step-by-step test case that verifies the password reset flow end-to-end.
   Reveal Solution Discussion Select an answer first
2. 22foundation · easy

   What is the goal of reviewing acceptance criteria for ambiguity?

   • ATo align the criteria with the technical design of the system
   • BTo shorten the criteria to make them easier to read
   • CTo ensure each criterion has a single, clear interpretation
   • DTo make the criteria more complex to cover all possible scenarios
   Reveal Solution Discussion Select an answer first
3. 23application · medium

   A team is starting a new feature. The product owner has a high-level idea, but the team has many questions about edge cases. Which collaborative technique is most effective for clarifying the acceptance criteria?

   • AAsk the product owner to write the acceptance criteria alone and share them with the team for review.
   • BDefer writing criteria until after development starts, so the team can learn from the implementation.
   • CHave the developers write the acceptance criteria based on their technical understanding.
   • DConduct an example mapping session with the product owner, developers, and testers to break the story into concrete examples.
   Reveal Solution Discussion Select an answer first