Definition of Done¶
Done-ness is defined differently at different stages of development and for different purposes.
Team Increment¶
Issue Type | Definition of Done |
---|---|
Story/Enabler | Code
Integration
Process
|
Spike | Documentation
Process
|
System Increment¶
Issue Type | Definition of Done |
---|---|
Feature/Enabler | Child Stories/Enablers
Documentation
Process
|
Spike | Documentation
Process
|
Solution Increment¶
Issue Type | Definition of Done |
---|---|
Capability/Enabler | Child Stories/Enablers
Documentation
Process
|
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.