"Back Interaction" for increasing stability and clearing dependencies in Dark Releases

[matbmoser]

Introduction

Give a "time" to finish features and to create stability and clear the dependencies at Dark Releases.
Plan only features/dependencies features for the "Main Releases"

The problem

The development teams need to overlap every 3 months the new features and dependencies clarification.
Creating a overhead at the dev team, causing that the quality of the features is reduced.

Solution Proposal

Create a "back interaction" or a "retrospective release" at the Dark Releases, to just focus on:

• Quality
• Stability
• Clear dependencies between expert groups/committees/architecture.

Propose Quality Gate for "Main Releases" only -> Approval from Security, Architecture, PO (Expert Group,Committee), etc..

No "central" quality group, the quality is responsibility from the Expert Groups, just the "Methods" shall be defined.

For example: how can a expert group proof the quality from their "products" with other stakeholders?

Open Topics

• Quality Team for KITs, Working Groups.

  • Under standards
  • Under reference implementations
  • Under "product" dependencies

• Show where are the quality responsibilities already documented in the working model.

• How can expert groups evaluate the quality of their products, how can the committee "approve" the quality (maybe with the architecture committee)