How to Measure Definition of Done to User Story – Your Ultimate Checklist

User Story – How to Measure Definition of Done

See Here Your Ultimate Checklist

If you are working with an Agile development model most of the chance you are working with User Story.

Let’s try to understand what methodology meaning of User Story before we will over the checklist of Definition of Done (DOD) to User Story.

The smallest unit of work is called the user story in an agile framework. It’s an end goal, not a feature, expressed from the software user’s perspective. 

Stories fit neatly into agile frameworks like scrum and kanban. In scrum, user stories are added to sprints and “burned down” over the duration of the sprint.

The stories are often written from the perspective of an end-user or user of the system.

Now you understand more what methodology definition of a user story.

As part of the development process improvement in an existing product, I required to define what definition of done for the user story for our development process.

After some deep research, I succeeded to create an ultimate checklist for DOD to User Story that could match your development process.

Definition of Done- User Story

• Requirements are completed (Technical, UI, Product
  Requirements).
  
• “Happy path” for the user story implemented by QA.
  
  
• Development Design Reviewed by relevant stakeholders.
  
  
• STP (Software Test Plan) reviewed by all relevant
  stakeholders (Product, Developer (BE and FE side), QA, Data Engineer, R&D Team Lead).
  
• Integration testing performed and compiled.
  
• The unit tests were written, executed, and passed.
  
  
• Code review is done by development team members.
  
  
• Incremental delivery to QA.
  
• End-to-End integration completed (by the developer).
  
  
• Automation tests reviewed (4 eyes review by a team member or team leader) and passed.
  
• Automation Functional tests, Regression, Validation, Negative, Load tests are passed.
  
  
• Non- functional requirements are met.
  
  
• The user interface implemented according to the design (the final micro-copy updated if needed).
  
  
• All bugs fixed.
  
  
• The manual configurations that need to be performed after the deployment to production are marked in the user story.
  
  
• The product owner accepts the User Story (PO approval).

Is this post helpful for you? Share your thoughts in comments on how it helped you. 

Join to Productive Hut Family and be part of a testing community!