A reminder for the developer and Product Owner to have a conversation is:

The correct answer is C. A User Story. In Agile, a User Story is intentionally kept brief - it is not a detailed specification but rather a placeholder for a conversation. The classic format ('As a [user], I want [goal], so that [benefit]') is a reminder that the full details, acceptance criteria, and nuances need…

Submitted by marco_it· Apr 18, 2026Agile Principles and Mindset

Question

Options

AThe Sprint planning meeting
BBacklog grooming
CA User Story
DAn Agile reminder

How the community answered

(22 responses)

B
5% (1)
C
91% (20)
D
5% (1)

Explanation

In Agile, a User Story is intentionally kept brief - it is not a detailed specification but rather a placeholder for a conversation. The classic format ('As a [user], I want [goal], so that [benefit]') is a reminder that the full details, acceptance criteria, and nuances need to be discussed between the developer and the Product Owner (or customer). This 'card, conversation, confirmation' model (the 3 C's of user stories by Ron Jeffries) means the story card itself is the trigger and reminder to have that deeper conversation, not a substitute for it.

Topics

#User Stories#Agile Communication#Product Owner Role#Developer Role

Community Discussion

No community discussion yet for this question.

Full PMI-ACP Practice