The following “Definition of Done” (DoD) guides the development teams to judge on the development of a piece of software (i.e., user story, task, bug, etc.) being finished or “Done”. Note that the DoD is a mindset and guideline rather than a checklist. Our goal and our own responsibility is to develop quality software. This DoD helps us to achieve this goal.
The continuous integration confirms the health of the software:
Known defects, if there are any, are reported in bug tracking system
In certain situations, some aspects of the definition of done may be a subject of compromise. Such exceptions and relaxations need to be agreed in the review meeting.
This definition of done handles embedded product code in the first place. For non-embedded code such as smartphone apps, server components, tools and scripts the definition of done may/should be tailored to meet the requirements of the particular case.