Definition of Done

Done-ness is defined differently at different stages of development and for different purposes.

The tables below describe the criteria that need to be taken into account by Product Owners (for Team Increment work), by Feature Owners (for System Increment), by Capability Owners (for Solution Increment work), and by Release Managers (TBC; for Software Releases).

Please note that when a Product/Feature/Capability Owner, or Release Manager marks a Story/Feature/Capability/Release as Done, all applicable criteria from the Definition of Done are expected to be fulfilled. When that is not possible, or applicable to an item, the Product/Feature/Capability Owner, or Release Manager MUST indicate in the comments why those elements of the Definition of Done do not apply to that Product/Feature/Capability or Release.

Failure to justify the lack of complete compliance with the Definition of Done result in decreasing quality, and increased Technical Debt, so please be very mindful of this Definition of Done.

Team Increment

Issue Type	Definition of Done
Story/Enabler	Code Supplied with an Acceptable License. Adheres to SKA language specific style. Checked into SKA repository with a reference to a JIRA ticket ID. Passes the CI/CD pipeline including compiling cleanly and being linted with no warnings: Linting. Unit and module tests pass with adequate coverage (>= 75% with appropriate exclusions for boiler-plate code). Component, integration and system tests (appropriate for the context) pass. Regression tests pass. Artefacts Packaged software artefacts are published to the Central Artefact Repository inline with SKA naming and semantic versioning standards. Code Documentation Exposed Public API (where applicable) is cleanly documented. Documented inline according to language specific standards. Deployed to externally visible website accessible via the Integration into the Developer Portal. Integration Deployed to a Continuous Integration environment (staging environment during Construction). Migrations are implemented with defined automated processes for roll-forward and rollback as appropriate. Process Peer-reviewed and integrated into the main branch via GitLab Merge requests. Relevant NFRs are met Satisfies acceptance criteria Accepted by Product Owner
Spike	Documentation Outcomes documented on the relevant SKA platform Documentation linked to issue in Jira Process Outcomes reviewed by relevant stakeholders Satisfies acceptance criteria Accepted by Product Owner

System Increment

Issue Type	Definition of Done
Feature/Enabler	Child Stories/Enablers Completed by all teams and integrated in an integration environment (staging environment during Construction). Documentation Solution Intent or project documentation updated to reflect the actual implementation. Process Satifies acceptance criteria Relevant NFRs are met Demonstrated to relevant stakeholders Accepted by Feature Owner
Spike	Documentation Outcomes documented on the relevant SKA platform Documentation linked to issue in Jira Process Outcomes reviewed by relevant stakeholders Satisfies acceptance criteria Accepted by Spike Owner

Solution Increment

Issue Type	Definition of Done
Capability/Enabler	Child Stories/Enablers Completed by all ARTs and integrated in an integration environment (staging environment during Construction) Documentation Solution Intent or project documentation updated to reflect the actual implementation Process Satifies acceptance criteria Relevant NFRs are met Demonstrated to relevant stakeholders Accepted by Capability Owner

Release

Issue Type	Definition of Done
TBD	TBD

Formally Controlled Project Documentation

Documents that are matured to the extent that they quantify an impact on safety, security, quality, schedule, cost, profit or the environment should be validated and formally controlled as per the SKA Document Creation, Validation and Release Standard Operating Procedure (SOP) (SKA-TEL-SKAO-0000765). Until such time, the Lightweight Document Process and Repository may used to manage these documents.

Thereafter, these documents must be formally reviewed and placed in the project’s configuration management system. Whilst there is an unavoidable overhead to this we aim to make it as efficient as possible. However, this level of documentation requires you to follow the process in the Configuration Management part of Confluence, specifically:

• Document number obtained by completing and forwarding the New Document Request Form to mailto:cm@skatelescope.org.

• Document is reviewed by suitable reviewer(s).

• Document is in eB and signed off.