The document discusses the definition of "done" and why it is important for software development projects. It provides multiple definitions that increase in level of completeness, from just having the code checked in to having the code fully tested, documented, packaged, and reviewed with all bugs closed. The definitions help ensure software meets quality standards before being considered finished.

1. Definition of „Done” Why do we need it ? Is one DoD enough ? What is it ?

2. Definition of „Done” Code completed and cheked in

3. Definition of „Done” Code completed and cheked in All unit tests passing Code reviewed

4. Definition of „Done” Code completed and cheked in All unit tests passing Acceptance tests satisfied Code reviewed

5. Definition of „Done” Code completed and cheked in All unit tests passing Acceptance tests satisfied Story accepted Deployed Code reviewed

6. Definition of „Done” Code completed and cheked in All unit tests passing Acceptance tests satisfied Story accepted Code coverage at 80%+ Deployed Code reviewed

7. Definition of „Done” Code completed and cheked in All unit tests passing Acceptance tests satisfied Story accepted Code coverage at 80%+ Deployed Code reviewed All bugs closed Stress tested

8. Definition of „Done” Code completed and cheked in All unit tests passing Acceptance tests satisfied Story accepted Code coverage at 80%+ Documented Deployed Performance tuned Code reviewed All bugs closed Stress tested

9. Definition of „Done” Code completed and cheked in DONE!? All unit tests passing Acceptance tests satisfied Story accepted Code coverage at 80%+ Documented Deployed Performance tuned Stress tested Packaged Code reviewed All bugs closed