Definition of Done

[fingeririna]

The Target of this Topic is to Esteblisch Definition of Done (DoD) checklist for a user story.

We decided to create the DoD in our Project and we are going to prepare a short list of areas, that we should control, to deliver the highest possible quality software.

To think ist also about the checklists DoD for Sprint, which help us in verification of our work on two stages of the software development process. DoD for Sprint is not part of this Topic.

• [x] Write document for checklist of DoD
• [x] Upload to repository -> rejected. DoD will be mentioned in each story

[TimmyAeberli]

Found a pretty cool but very technical DoD example as a README.md on github

I believe it would be worthwhile to have it in our README.md as it should be very close to the code. Let me know what you think. @fingeririna

I would formulate DoD (Story) as:

• [ ] Produced code for presumed functionalities
• [ ] Assumptions of User Story met
• [ ] Project builds without errors
• Unit tests written and passing
• [ ] Project deployed on the test environment identical to production platform
• [ ] Descriptive pull request text, answering:
• What problem/issue are you fixing?
• What does this PR implement and how?
• [ ] Tests on devices/browsers listed in the project assumptions passed
• [ ] Feature ok-ed by UX designer
• [ ] Feature is tested against acceptance criteria
• [ ] Feature ok-ed by Product Owner
• [ ] Refactoring completed
• [ ] Any configuration or build changes documented
• [ ] Documentation updated
• Record actual time taken for the task in the PR
• Update the README.md with any changes/additions made
• [ ] Peer Code Review performed or Assign your PR to someone for a code review
• This person will be contacted first if a bug is introduced into master

[fingeririna]

The definition of done is a list of criteria that has to be met before any work can be considered as done. Failure to meet any one of these conditions means the work is not complete.

A task/story/bugs will not be considered to be complete until all these items can be checked off.

• [ ] Story is tested against acceptance criteria
• [ ] Unit test should be passed
• [ ] Integration test is done ( if applicable)
• [ ] Non-functional requirements are met
• [ ] Story ok-ed by Product Owner
• [ ] Peer Code Review performed
• [ ] Any configuration or build changes documented
• [ ] any database changes are documented in Database

[fingeririna]

Extension of the DOD:

• [x] any Database changes are documented in Database

Update also confluence page https://wiki.akros.ch/pages/viewpage.action?pageId=116819943