[tractusx-dev] R24.12 next steps in refinement phase

[Stephan Bauer <stephan.bauer@xxxxxxxxxxxx>]

Dear Community,

 

As discussed in the last Office hour, here is some more information about the collaboration between Tractus-X/Catena-X and the next steps.

 

Last week the Catena-X Committees and Expert Groups had a workshop to discuss and agree on “roadmap items” for 24.12. The roadmap items are on a management level which result (during refinement phase)  in Tractus-X (open-source) topics and Catena-X (standards, whitepapers)

 

• Now we are in the refinement phase

It is important to work together during the refinement phase. Committees and expert groups are responsible for creating the features (requirements). They support the features throughout the entire release and contribute their expertise. The open-source community is essential for the technical part and must be involved in the refinement of the features (especially the committers). Without a committer, the feature won't make it into the release.

 

Terminology: roadmap items should be linked to one or more features (on the sig-release board) A feature should be linked with one or more User Stories/Subtasks (issues in product-specific repositories)

 

The different topics:

 

Tractus-X

e.g. Kits, Reference Implementation, API Specification, Protocols, Sample Data, Architecture, Documentation, Deployment Scripts, Tutorials etc.

 

The roadmap items must be broken down into features by creating one or more issues in the sig-release repository. First, it’s a “feature proposal.” To avoid confusion, keep the following guidelines in mind for each feature you create:

• MUST set the label “Prep-R24.12” (only issues with this label will be considered in the refinement/release planning).
• MUST keep the status on “Inbox” until the feature met the Definition of Entry
• SHOULD set additional labels to highlight dependencies to other components (e.g. portal, edc …)
• MUST NOT set the Milestone. This is done together during planning days
• SHOULD include as much detail as possible in the issue. Please refer to the Definition of Entry (DoE) for guidance.
• MUST add a link to the new generated issue in the corresponding roadmap item
• MUST link the supporting Group with filed supported-by (open the feature → right box “Release Planning”). If your Expert Group is not available, please select the committee 

 

If a feature is further broken down into tasks by adding issues in the component repositories, these issues MUST be linked to their parent feature proposal. For creating the component issues, the related/needed contributor/committer is responsible.

• Important, please talk to each other. Explain the features (requirements) and create dedicated component issues

Milestone Events:

• Refinement Day 1: Initial refinement, dependency discussion. It’s dependent on the features on the board. ⇾ This meeting will be skipped due to the short delay from now
• DRAFT Feature Freeze: No new feature proposal is allowed after this date
• Refinement Day 2: Further refinement, dependency discussions, status update and validation, setting the status to “Backlog” upon meeting entry criteria.
• Planning Days: Present the features which already met the DoE. The milestone is set to 24.12 if the audience agrees on it.  Features with milestone MUST now have a committer and all dependencies MUST be resolved.

 

Catena-X (just in case this information is useful for you ⇾ it's NOT open source, but a standard request can be needed because of …)

… e.g. Standards (cause of adaptations in Semantic Models, Logic/Schema, API Specification, Protocols), Whitepaper (which might end up in a Kits adaptation) etc.

 

A detailed description of the change request or new standard request is needed and should be refined during the refinement phase. The detailed description needs to be discussed during the planning days with the audience (Committees and Expert Groups) and especially with the TC4S (Technical Committee 4 Standardization). All dependencies MUST be identified/discussed/aligned.

 

All requests MUST be submitted to TC4S for approval within CX Houston at latest 1. August. If the request is approved, the applicant will receive their branch in the standardization repository (within Catena-X e.V. GitHub Organization) to work on the standard.

 

Milestone events:

• Standards Planning (same dates as Release Planning): In this event, dependencies of the requests to other standards MUST be identified the latest. All committee and expert members will be invited to this meeting.
• Deadline for standard requests (1^st August 2024): On this day, all standard requests in CX Houston MUST be submitted. A later submission of a standard request will be rejected by default!

Greets 

 

Stephan

 

 

Stephan Bauer 

Platform Domain Manager

 

Catena-X Automotive Network e.V. 
Reinhardtstr. 58 • 10117 Berlin 
Tel: +49 30 53607799  Mobil +49 151 67353921 

stephan.bauer@xxxxxxxxxxxx 

 

 

 

Folgen Sie uns auf LinkedIN 

 

Vereinsregister beim Amtsgericht Berlin (Charlottenburg) Nr D1537 

Vorstandsvorsitzender: Oliver Ganser 

 

Book a meeting with me