What are two examples of additional content that need to be added to the user story before it can be considered complete?

A partially created user story for an approval task has been added to the Product Backlog and you have been asked to review it.

So far, the user story includes acceptance criteria stating:

"Verify that the user can select approve or deny."

"Verify that the user can enter an approval comment."

What are two examples of additional content that need to be added to the user story before it can be considered complete?
A . Condition upon selecting either "deny" or "approve"
B . User story description
C . UI mockup
D . Truth table

View Answer

Answer: AB

Explanation:

User Story Description (B): A complete user story should include a detailed description that outlines the context, goals, and specific actions the user can perform. This helps in setting a clear understanding of what needs to be developed and why. The description provides the foundation for the user story and ensures that all stakeholders have a shared understanding of the requirement.

Reference: Appian Documentation – Writing User Stories

Condition upon Selecting Either "Deny" or "Approve" (A): To ensure that the user story is complete, you must specify what happens when the user selects "deny" or "approve." This could include conditions such as sending notifications, triggering workflows, or updating statuses. Clearly defining these conditions ensures that the development team knows exactly what to implement and how the system should behave in different scenarios.

Reference: Appian Documentation – Acceptance Criteria Examples