Good morning everybody,
Friendly reminder about the
Alignment day (former refinementday 2) next Wednesday.
As written in the mail before (please look down) the agenda is up to you. Only features are discussed, where
you have some questions.
- Essential:
- Only features labeled
“Open Discussion” will be considered.
- This label must be set
at least three days before the Dependency Day to enable structured planning and discussion.
- The Alignment Day is NOT a planning.
- The Eclipse Tractus-X webpage cannot be used to inform you, because we are in a maintenance phase. Please keep informed via
- Current
board for 25.09 -> 23 features and only
1 with the tag open question => assumption: for all the other features, the dependencies, resources etc. are clear.
Why should you have questions, there are two options/role:
Are you a feature owner, and you have some questions about your dependency components (components which are needed to fulfil your requirements
⇾ you probably need help from other developers, which have experience with this specific component)
Are you as “component” tagged to a feature
⇾ you might have the question to the feature owner what the feature owner needs from your side
😉
If there are no questions … also fine… we will have a brief introduction and afterward we will close the meeting.
Greets Stephan
From:
tractusx-dev <tractusx-dev-bounces@xxxxxxxxxxx> on behalf of Stephan Bauer via tractusx-dev <tractusx-dev@xxxxxxxxxxx>
Date: Wednesday, 2. April 2025 at 08:51
To: tractusx-dev@xxxxxxxxxxx <tractusx-dev@xxxxxxxxxxx>
Cc: Stephan Bauer <stephan.bauer@xxxxxxxxxxxx>
Subject: [tractusx-dev] Realignment of the Eclipse Tractus-X Refinement Days
Dear Eclipse Tractus-X Community,
We would like to inform you that the
Refinement Day 1 on April 9th will not take place! Instead, teams will have more time to further develop and refine their features independently.
The Refinement Day 2 (April 30th) will be repurposed as an
Alignment Day (just a renaming and focus change) to address questions regarding specific features and their dependencies.
It is important to note that no features will be refined during this session. The focus will be on
alignment between teams concerning dependencies and questions.
Key Organizational Points:
- If you like to discuss your feature or your dependency during the Alignment Day, please add the
label “Open Discussion”
- Three days before the Dependency Day, the agenda will be finalized based on the
feature labels “Open Discussion.”
- We will organize 30 min (or less) slots per “product”, based on the
label “Open Discussion.”
- Feature Owner: If you are a Feature Owner, please ensure that relevant teams are informed about dependencies.
⇾ Tagged with labels on feature
- In this case, tagged „teams“/labels should have the possibility to ask for their needed contribution to this feature and do their task break down and in the end,
a resource planning
- The feature owner is always responsible to inform and collect the information for the feature
⇾ ready refined
- Only features labeled
“Open Discussion” will be considered.
- This label must be set
at least three days before the Dependency Day to enable structured planning and discussion.
- The Alignment Day is NOT a planning.
- The Eclipse Tractus-X webpage cannot be used to inform you, cause we are in a maintenance phase. Please keep informed via
What Has Changed Compared to the Previous Refinement Days?
- Refinement is now fully team-driven: Teams are responsible for refining their features before the Alignment Day.
- No brainstorming or feature-building during the session: The focus is solely on discussing dependencies and ensuring cross-team
alignment.
- Early planning is essential: Teams must proactively refine features and label dependencies
before the session to avoid last-minute issues.
Our goal with this adjustment is to
improve team alignment, clarify open questions early, and efficiently address dependencies and also save your time
If you need any clarification, please feel free to reach out.
Best regards,
Theresa and Stephan.
