In agile practice, a User Story is often framed by the “3 Cs”: Card, Conversation, and Confirmation. The Card captures just enough of the requirement to spark dialogue. The Conversation is the collaborative discussion among Product Owner (or Customer/Business), Developers, and other stakeholders that elaborates details and clarifies intent. The Confirmation element records the specific, testable acceptance criteria that will be used to verify the story delivers the intended outcome for its beneficiary (the user or customer). These acceptance criteria translate stakeholder expectations into objective checks—often articulated as scenarios or examples—that determine whether the story is fit for purpose and “Done.” Agile Project Management approaches (including AgilePM/DSDM and Scrum-aligned practices) emphasize that acceptance criteria belong with the story as its Confirmation, because that is what allows the team to assert value delivery, guide development and testing, and anchor Sprint Review demonstrations. Therefore, the appropriate place to record the concrete measures by which a user can successfully use the delivered capability is the Confirmation section of the User Story.