CPOA User Stories and Acceptance Criteria 3

Question 1

Which story-splitting technique divides a large user story based on the sequential steps a user takes to accomplish a goal?

Accepted Answer

Split by workflow steps

Answer

Split by data variations

Answer

Split by business rules

Answer

Split by acceptance criteria

Question 2

Which of the following is an example of a non-functional acceptance criterion?

Accepted Answer

The page must fully load within 2 seconds under standard network conditions

Answer

The user can log in using their registered email address and password

Answer

The system displays a validation error message when an invalid email format is entered

Answer

The user receives a confirmation email after successful account registration

Question 3

What is the primary purpose of using story points for effort estimation?

Accepted Answer

To measure team velocity by tracking relative effort and complexity across stories

Answer

To calculate the exact hours each team member needs to spend on each story

Answer

To determine the exact cost of implementing each user story

Answer

To rank user stories by their business priority in the backlog

Question 4

What is the primary use of the Given-When-Then format when writing user story acceptance criteria?

Accepted Answer

To write scenario-based acceptance criteria in a structured, testable format

Answer

To document technical architecture and design decisions for the development team

Answer

To prioritize user stories in the product backlog by business value

Answer

To estimate the complexity and effort required to implement user stories

Question 5

A user story is marked as 'Done' in a sprint. What does this correctly signify?

Accepted Answer

The story meets all story-specific acceptance criteria AND satisfies the team's Definition of Done

Answer

The developer has finished writing the code for the feature

Answer

The product owner has scheduled the story for the next production release

Answer

The story has been reviewed and approved by external stakeholders in a formal session

Question 6

Which approach best ensures that acceptance criteria are testable and verifiable?

Accepted Answer

Expressing them as observable, verifiable behaviors with specific expected outcomes

Answer

Writing them in technical terms that developers can directly implement

Answer

Keeping them intentionally broad to allow flexibility in how they are implemented

Answer

Using story points to quantify and measure each acceptance criterion numerically

Question 7

What is the product owner's role regarding acceptance criteria during a sprint review?

Accepted Answer

To verify that the delivered work meets the acceptance criteria and formally accept or reject it

Answer

To document all technical decisions made by the development team during the sprint

Answer

To rewrite acceptance criteria based on developer feedback received during the sprint

Answer

To assign acceptance criteria testing responsibilities to specific team members