Refinement Day 2 for Release 25.03

Hello, Eclipse Tractus-X Community!

We are excited to announce Refinement Day 2, taking place on November 6th, from 09:05 to 12:00. This session will build on the work from Refinement Day 1 and focus primarily on the identified dependencies. These dependencies, which were highlighted by the labels on the features during Refinement Day 1, will be the center of attention for this event.

You can still continue refining features as necessary, but our main focus for this session will be resolving these dependencies to ensure smooth progress toward Release 25.03.

The Teams session links and breakout groups remain the same as on Refinement Day 1. You can find the overall Teams session link and more information on the open-meetings page.

Agenda for Refinement Day 2

Here’s the plan for the day:

• 09:05 - 09:30: Welcome, Introduction, and Expectations
• 09:30 - 11:15: Refinement in dedicated groups, grouped by expert groups
• 11:15 - 11:45: Presenting the results, grouped by expert groups
• 11:45 - 12:00: Closing and Next Steps

Group Work & Presenting Results

During the refinement sessions, each group will focus on resolving identified dependencies from Refinement Day 1, which are visible via the related labels on the features. While further feature refinement is allowed, the emphasis is on addressing and coordinating dependencies between groups and components.

Our working Board for the day is the Release Planning - R25.03 - Preperation

You’re encouraged to collaborate across groups as needed, and we’ll provide Teams sessions (we will use the same sessions from Refinement Day 1) for each group to work in. It might be the case for some experts to jump into different other groups to resolve dependencies.

Important for the session:

• Use the feature template to structure your work
• Identify dependencies with other components or groups and add the correct labels to the features
• Use the supported-by field to map the feature with your expert group
• help each other to solve/analyze dependencies

At the end of the refinement session, we’ll regroup and present the progress made. Each expert group will present their refined features, focusing on what’s been developed so far and the key insights.

note

If the feature is ready refined, the status should be set to Backlog-> this should by an alignment, between the requesting Expert Group/Committee and the open-source community.

Committee/Expert Groups and Teams Sessions:

tip

The sessions for the committees can be used to sync within the underlying expert groups. Feel free to switch between groups if necessary!

• Network Service Committee
  • Business Partner Data Management
  • Self-Sovereign Identity
  • Dataspace Connectivity
  • Digital Twins
  • Company Certificate Management
• Sustainability Committee
  • Digital Product Pass
  • Circularity
  • Product Carbon Footprint - Methodology & Verification
  • Product Carbon Footprint - Architecture & Interoperability
  • Product Carbon Footprint - on Electronics
• Product Lifecycle, Quality and Resiliency Committee
  • Traceability
  • Demand & Capacity
  • Online Simulation
  • PURIS
  • Data-driven Quality
• Industry Core Committee
• Architecture Management Committee
• Data Space Operations Committee
  • Data Sovereignty
• Working Groups
  • Data Integration Pattern

note

Feel free to switch between groups if necessary!

Special Note for KITs

For KITs, we understand that not all sections of the template are necessary right now. The most important things to include at this stage are:

• The Feature Team responsible for the work
• A brief explanation of the feature (just 2 sentences)

Next Steps & Release Planning Days

By the end of the session, we expect to have features ready refined. It might be the case, not all are fully refined but will be in good shape for further refinement and proactive work until we will meet again for the Release Planning Days

We look forward to a productive Refinement Day - Happy Refining! 🚀