[OSDU Data Flow] Definition of Done

In the spirit of Continuous Delivery, we will prioritize completing and deploying into production new services/features over taking on new work from the backlog.

Definition of Done

The OSDU Data Platform Data Flow Services has the ambition of continuous delivery and thus has the ambition of continuous done. Because of this, Done has a stronger contract at a feature level than it does at a service level.

Stories

We will capture the user stories here so that we have a user-centric view of done.

Feature Done

A feature is not done until it is running and validated on multiple cloud platforms and ready for consumption. A feature will be:

• implemented
• tested
  • Unit
  • Compliance
  • Integration
  • Workflow / dataflow tested
• documented
  • Internal for code maintenance
  • API
  • Usage
• deployed

Given the multi-platform deployment requirements, we will consider feature done from a common code perspective once it is demonstrated on two or more cloud platforms. It will be done from the OSDU Forum perspective once available on all supported platforms. This distinction allows OSDU platform deployments to move a slightly different speeds to allow early feedback in a production environment.

Service Done

Continuous delivery requires continuous backlog pruning and thus there is no preconceive notion of done. That is a idealized statement that is only true once a system has reached a level of maturity allowing autonomous delivery of services.

For Release 3 we will define a specific scope of work which will be documented both in narrative form as well as issues. See Release 3 Planning.