What is the primary purpose of acceptance criteria in a user story?

To define the technical architecture for implementation

To clarify the scope and provide conditions for verifying the story is complete

To estimate the story's complexity

To assign ownership of the story to a team member

During a story-writing workshop, the product owner notices that stakeholders are writing stories that are too technical and lack business value. What should the product owner do to guide the team?

Assign the stories to developers to rewrite

Remove the technical stories from the backlog

Approve the stories as written to avoid conflict

Ask stakeholders to rewrite the stories using the 'As a... I want... so that...' format

A team has a large story: 'As a user, I want to manage my orders so that I can track and modify them.' The story includes viewing orders, canceling orders, and changing shipping addresses. The product owner wants to deliver the most common use case first. What is the best split?

Do not split; deliver all at once

Split by technical layer: UI, service, data

Split by priority: high, medium, low

Split by use case: view orders, cancel orders, change address

A team is planning a large user story: 'As a user, I want to manage my profile so that I can keep my information up to date.' The story includes viewing, editing, and deleting profile fields. The product owner wants to deliver value early. Which approach best splits this story while preserving business value?

Split by user role: admin, regular user, guest

Split by feature: view profile, edit profile, delete profile

Split by technical layer: database, backend, frontend

Split by data field: name, email, phone

What is the main goal of splitting a large user story into smaller stories?

To assign each story to a different team member

To deliver value incrementally and enable faster feedback

To eliminate the need for acceptance criteria

To reduce the total amount of work

Certified Tester Foundation Level Agile Tester

Domain 1Objective 5

Collaborative User Story Creation CT-AT Practice Questions (Page 3)

Part of the Agile Software Development domain, which makes up ~37% of our current practice bank.

28questions here

6free pages

7concepts

Questions 11–15

11foundation · easy
What is the primary purpose of acceptance criteria in a user story?
Select an answer first
12application · medium
During a story-writing workshop, the product owner notices that stakeholders are writing stories that are too technical and lack business value. What should the product owner do to guide the team?
Select an answer first
13application · medium
A team has a large story: 'As a user, I want to manage my orders so that I can track and modify them.' The story includes viewing orders, canceling orders, and changing shipping addresses. The product owner wants to deliver the most common use case first. What is the best split?
Select an answer first
14expert · hard
A team is planning a large user story: 'As a user, I want to manage my profile so that I can keep my information up to date.' The story includes viewing, editing, and deleting profile fields. The product owner wants to deliver value early. Which approach best splits this story while preserving business value?
Select an answer first
15foundation · easy
What is the main goal of splitting a large user story into smaller stories?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to CT-AT

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by ISTQB. “CT-AT” is a trademark of its owner, used for identification only.