Definition

ref: link Scrum defines the Definition of Done in pretty simple terms: it’s the acceptance criteria that are common to every single user story.

  • The definition of “done” depends on the task.

In Agile Software Development, we use the User Story Definition Of Done(DOD) for User Stories to ensure the quality of work and to assess whether the team completes a User Story or not. If respected, the Definition of Done (DOD) in Scrum is keeping the development team away from the .

ref: link

Predictability is key in Agile.

But how does the User Story Definition Of Done (DOD) in Scrum contribute to predictability?

I mainly call a user story DONE when it is ready to be released to the users if wanted. There are no more merges, no documentation, no further testing, nothing else. That means that:

  1. there is a precise inventory of the part of the scope that you completed,
  2. the users can start using the results of the stories and
  3. the company can start cashing in the return of investment of this user story,
  4. the company can sell the feature or can attract more clients
  5. the is room for improvement, and the stakeholders can suggest already new features
  6. there is progress

Example, User Story Definition of Done (DOD): A story can be marked as Done when:

example 1

  • The user story implementation meets ALL the acceptance criteria
  • The Product Owner approved the user story
  • The user story is deployed in Production environment but deactivated (toggle off)
  • The unit tests were written, executed and passed
  • Every acceptance criteria have at least a test case associated
  • The team wrote, completed unit tests and they passed
  • The Technical Documentation is uploaded by the team on Confluence
  • The performance is under X
  • There is no regression in the automation testing suite
  • The user story has been peer-reviewed
  • Integration testing performed and compiles
  • The manual configurations that need to be performed after the deployment to production are marked in the user story
  • The deployment to the production environment of the story has release notes
  • End-user documentation is available
  • The user interface is according to the design
  • The code refactoring is completed
  • Marketing communication of the changes are documented