User story structure, acceptance criteria, Definition of Done

 A user story in Agile typically consists of these key parts: 

"As a [user role], I want to [action], so that [benefit]" which includes the user persona, the desired action, and the expected value or outcome, and is often further detailed with "acceptance criteria" to clearly define what constitutes a completed story; essentially focusing on the "who," "what," and "why" of a feature from a user's perspective.


User story examples: What is User Story and Acceptance Criteria (Examples) https://www.softwaretestinghelp.com/user-story-acceptance-criteria/

"Definition of Done (DoD)" is a set of standardized criteria that a user story must meet before it can be considered "done" and closed, acting as a checklist to ensure consistent quality across all user stories within a project, while "acceptance criteria" are specific requirements tailored to each individual user story, defining the conditions under which that particular story will be considered acceptable by the customer; essentially, DoD applies to all user stories while acceptance criteria are unique to each story.



This page has: 

(1) Examples for acceptance criteria . 

(2) Different in Acceptance criteria and 'Definition of Done (DoD' 

 https://www.techagilist.com/agile/product-owner/acceptance-criteria-for-user-stories-with-examples


Additional info:

Short and concise article:

https://www.romanpichler.com/blog/10-tips-writing-good-user-stories/

----------


Author:  Dr M Khalid Munir, a Product Management professional working for the healthcare solutions industry for about two decades. email: khalid345 (at) g m a i l (dot) com

 

Comments

Popular posts from this blog

Beyond Google: The Best Alternative Search Engines for Academic and Scientific Research

LLM-based systems- Comparison of FFN Fusion with Other Approaches

Product management. Metrics and examples