Explain the definition of "Done" in Agile Methodology | Agile Methodology Tutorial

Explain the definition of "Done" in Agile Methodology | Agile Methodology Tutorial

In this article, you will learn about the definition of done in agile methodology.

In agile methodology, the definition of done is defined into three different stages known User story (Requirement), Iteration, and product release. 

Let’s discuss them in brief:

User Story (requirement)

The user story stands for the requirements which are described in a few sentences. The user requirements are the general language of the user. The user story should be completed in each iteration. The story of the user is done when:

• The complete code and documentation have been checked-in. 
• The product needs to pass all the processes of the unit test. 
• All the processes of the acceptance test case have been moved to the next stage.
• The product owner must accept the user story.
• The documentation is written in the user story.

Iteration

An iteration is a time-based collection and execution period of the user story. It works on the defects or bugs in the product and manages the release date of a product. Iteration is defined at the time of iteration planning meetings and completed within the demo and review meeting. The iteration is also known as sprint. The repetition is required when:

• The team is testing the performance of the product. 
• Product backup is done.
• User requirement has been accepted or moved for the next phase of the iteration.
• Defects on the product have been identified, fixed, or postponed for the next iteration.

Release

The product release is a big occasion that represents both internal and external delivery of the work. It also tests the version of the product or system. The product release is only possible when:

• The system is stress tested and it comes up to the mark.
• The performance of the product is high.
• Contain the validation of the security in the product. 
• Disaster recovery plans are tested.