Merge pull request #168 from catenax-eV/update-from-working-model-5d8…

…2ecd

Update from Working-model: 5d82ecd

docs/working-model/ecosystem/ecosystem.md

@@ -29,7 +29,7 @@ The Association is complemented by the **development environment**. The focus of
 
 ## Operating environment
 <!-- markdown-link-check-disable -->
-In the **operating environment**, the various open source and commercial services and business applications are operated by different providers. A detailed description of the [provider roles](../../operating-model/who-roles-in-the-catena-x-ecosystem/who-roles-in-the-catena-x-ecosystem.md) and the associated [software components](../../operating-model/what-service-map/what-service-map.md) can be found in [Operating Model](../../operating-model/why-introduction/why-introduction.md).
+In the **operating environment**, the various open source and commercial services and business applications are operated by different providers. A detailed description of the [provider roles](/docs/next/operating-model/who-roles-in-the-catena-x-ecosystem/) and the associated [software components](/docs/next/operating-model/what-service-map/) can be found in [Operating Model](/docs/next/operating-model/why-introduction).
 <!-- markdown-link-check-enable -->
 The Catena-X Association publishes standards with the goal of enabling interoperability, data sovereignty, and security for all participants in the data space. The ecosystem participants must comply with the standards published by the Catena-X Association in order to work with the data space. Catena-X standards build on Gaia-X / *International Data Space Association* (IDSA) concepts and principles, industry standards, and best practices, among others, and extends these by automotive domain and use case specific requirements. By certifying ecosystem participants and software components the Catena-X Association ensures transparency and trust in the ecosystem. A certification testifies, for example, that a software component is interoperable, data sovereign and safe to use in the Catena X data space.
 

docs/working-model/organizational-structure/catena-x/catena-x.md

@@ -37,13 +37,13 @@ An [Association Member](#association-member) can acquire additional roles by joi
 |  |  | Management board |  | Committee |  |  | Expert Group |  | [Catena-X office](catena-x-office.md) |
 |---|---|---|---|---|---|---|---|---|---|
 |  |  | Member | [Sponsor](management-board.md#board-sponsor) | [Lead](committee.md#lead-and-co-lead) | Member | [Mentor](committee.md#mentor-for-expert-groups-optional) | Lead | Member |  |
-| Strategy | [Develop and maintain the Association strategy](management-board.md#association-strategy) | A | D | I |  |  | I |  | C |
-|  | [Develop and maintain the business domain strategy](committee.md#business-domain-strategy) | I | A | D | C |  | I | I | C |
-|  | [Develop and maintain a strategy on functional level](expert-group.md#functional-level-strategy)  |  | I | A |  | C | D | C | C |
+| Strategy | [Develop and maintain the Association strategy](management-board.md#association-strategy) | A | D | I |  |  | I |  | |
+|  | [Develop and maintain the business domain strategy](committee.md#business-domain-strategy) | I | A | D | C |  | I | I | |
+|  | [Develop and maintain a strategy on functional level](expert-group.md#functional-level-strategy)  |  | I | A |  | C | D | C | |
 | Mgmt. of association bodies | Setup Committees | D, A |  |  |  |  |  |  | C |
 |  | Close Committees | A | D | C | I |  |  |  |  |
-|  | Setup Expert Groups |  | I | A | A | D |  |  | C |
-|  | [Close Expert Groups](expert-group.md#closing-of-expert-groups) |  | I | A |  | D | A | A | C |
+|  | Setup Expert Groups |  | I | A | A | D |  |  | |
+|  | [Close Expert Groups](expert-group.md#closing-of-expert-groups) |  | I | A |  | D | A | A | |
 | Development | Propose new feature requests |  |  | C  | C | C | A | D |  |
 |  | Approve features requests) |  |  |  | I | I | D | A,C |  |
 |  | Track the progress of the feature) |  |  |  | I | I | D | A,C |  |

docs/working-model/organizational-structure/catena-x/expert-group.md

@@ -3,100 +3,98 @@ sidebar_position: 3
 title: Expert Group
 ---
 
-The aim of the Expert Groups within the Catena-X Automotive Network e.V. is to develop results together with the members in line with the association's strategic direction. The Expert Groups are initiated and managed by the related Committee. Depending on their scope, Expert Groups do not exist forever. They work on dedicated topics, present the results to the Committee and are then [retired](#iii-closing). If a follow up is required, a new Expert Group has to be initiated.
+The aim of the Expert Groups within the Catena-X Automotive Network e.V. is to develop results together with the members in line with the association's strategic direction. The Expert Groups are initiated and managed by the related Committee. Depending on their scope, Expert Groups do not exist forever. They work on dedicated topics, present the results to the Committee and are then [retired](#3-closing). If a follow up is required, a new Expert Group has to be initiated.
 
 ## Expert Group Life Cycle
 
 ![Expert Group Lifeline](../assets/expert-group-life-line-v2.drawio.svg)
 
-The life of an Expert Group is devided into three phases:
+The lifecycle of an Expert Group is divided into three phases:
 
-I. [Initiation](#i-initiation)
-II. [Working Phase](#ii-working-phase)
-III. [Closing](#iii-closing)
+1. [Initiation](#1-initiation)
+2. [Working Phase](#2-working-phase)
+3. [Closing](#3-closing)
 
 The overview of the existing Expert Groups can be found in the [organizational chart](https://catena-x.net/fileadmin/user_upload/06_Ueber_uns/Ueber_uns_der_Verein/Catena-X_Organization_Chart.pdf) on the Catena-X homepage.
 
 The product strategy involves the specific operational activities within a Expert Groups in collaboration with the committee. It deals with the tactical day-to-day tasks and processes that need to be executed to support the business domain strategy.
 
 The focus lies on implementation, realization and the delivery of tangible results.
 
-### I. Initiation
+### 1. Initiation
 
 1. **Request Submission**: Interested individuals or organizations seeking to form an Expert Group may submit their requests to the Catena-X Association. These requests will be assigned to a committee for consideration. The committee will add the request to its agenda for validation.
 2. **Validation and approval**: The committee will conduct an initial validation of the request. If deemed valid, the requester will be required to submit a one-page document outlining the challenge the Expert Group aims to address, the current status, and the objectives the group should achieve. This document ensures a clear understanding of the group's goals and scope.
-3. **Application Phase**: The one-page document serves as the foundation for the Application Phase. Employees of association members are invited to apply for a seat in the Expert Group. Members of the group will be selected based on predefined criteria.
+3. **Application Phase**: The one-page document serves as the foundation for the Application Phase. Employees of association members are invited to apply for a seat in the Expert Group. From the pool applicants, the [Core Group members](#core-group-member) will be selected based on predefined criteria.
 4. **Notification and Kick-Off**: All applicants will be informed of the outcome of their application (core team, review team, or rejected). Core team members will be invited to a kick-off meeting for the group's inaugural session, typically scheduled two weeks after the conclusion of the application phase.
 
-### II. Working Phase
+### 2. Working Phase
 
 During their working phase, Expert Groups are expected to continuously develop and advance their assigned topics. This involves regular meetings, collaborative research, and consistent communication among members to ensure progress. Additionally, planned work and results should be regularly shared within the association to promote transparency and collective insight. The groups should also provide periodic updates to the committee, highlighting key milestones, challenges encountered, and any adjustments to their objectives. Active engagement and a commitment to innovation and improvement are essential to the success of the Expert Groups in achieving their goals. The [committee mentor](./committee.md#committee-and-expert-groups) guides the Expert Group and reports back to the committee on progress. The committee will review the outcomes for strategic fit of Catena-X.
 
 The working phase should be viewed as a cyclical series of regular activities that align with the [release cycles](../../process-structure/process-structure.md) and its phases of the association.
 
 The composition of the Expert Groups is not static and is expected to change over their life time. In any case people that want to join an existing Expert Group need to be approved the same way, as applicants for new Expert Groups. If a Expert Group member is stepping down from its position, it cannot be handed over to another employee of the same company.
 
-### III. Closing
+### 3. Closing
 
 Once a Expert Group delivered its dedicated topic, a regulated closing takes place. The Committee validates the results of the Expert Group as after the closure of the Expert Group, the responsibility for the topic transitions to the Committee. When the results are validated, the Expert Group is then officially discharged and closed by Committee.
 
 A final documentation of the work results on the digital collaboration platform is mandatory, and every Expert Group member is required to contribute to this. The documentation is to be made accessible to every member in coordination with the office.
 
-## Expert Group Roles
-
-### Expert Group Leads
-
-The Leads serve as the primary points of contact, ensuring the effective delivery of the product strategy by the Expert Group.
-They have the authority to delegate tasks and create additional roles as needed.
-The Leads are tasked with:
+## Expert Group Responsibilities
 
-- monitoring member participation
-- escalating issues with underperforming members
-- maintaining cohesion and coordination within the Expert Group to align with the Committee's objectives
+### Vision and Mission
 
-### Expert Group Member
+To ensure a structured and predictable development of their use case, Expert Groups must create and maintain a clear, forward-looking plan with the following timeframes:
 
-Responsibilities of the Expert Group members include:
+- **3 Years:** Outline a compelling and ambitious vision for the long-term future of the use case. This vision should inspire and set a clear direction.
+- **12 Months:** Based on the vision, summarize the key steps planned for the upcoming year. Focus on high-level objectives and what users will gain, ensuring consistent and predictable progress for adopters.
+- **3 Months:** This plan aligns with the release planning, providing specific details on immediate actions and deliverables.
 
-- active participation in meetings and discussions
-- timely execution of assigned tasks
-- sharing of relevant knowledge and best practices
-- maintaining effective collaboration and coordination within the group
-- continuously seeking opportunities for improvement
+### Release DACI for Expert Groups
 
-An Expert Group Member plays an active role in shaping decisions, offering input, and collaborating with others to achieve the Expert Group goals. The experts will familiarise themselves with the implementation in Eclipse Tractus-X and the respective standards and KITs. They attend meetings, participate in discussions, and contribute to the planning and execution of tasks. An Expert Group Member is responsible for taking hands-on actions by actively contributing to the development of standards, KITs, and/or reference implementations.
+|Phase|Process|Expert Group role|Explanation|
+|---|---|---|---|
+|Preparation|[Roadmap Preparation](../../release-management/planning/cx-roadmap-preparation.md)|Driver|Prepare a roadmap for the expert group, including features, newly proposed Catena-X standards or changes to existing standards, and KITs. Communicate and discuss the roadmap with the assigned committee and reviewer group.|
+||[Release Roadmap Review](../../release-management/planning/cx-release-roadmap-review.md)|Driver|Present the Roadmap items to the broader audience within the association, to inform them and get feedback about the intended work.|
+|Planning|[Feature proposal creation](../../release-management/planning/tx-feature-proposal-creation-approval.md)|Driver|Break down intended work in Eclipse Tractus-X into features.|
+||[Feature proposal refinement](../../release-management/planning/tx-feature-proposal-refinement.md)||Update Git issues for the planned features and Kit changes in sig-release. Prepare open planning during the refinement phase.|
+||[Release planning days](../../release-management/planning/tx-release-planning-days.md)||Discuss and present Git issues and standardization requests during Open Planning and lead dependency planning.|
+||[Standard Request Creation](../../release-management/planning/std-standard-request-creation.md)||Create standardization or change requests using the Houston tool.|
+|Development|Development||Track the development of features throughout the Catena-X release.|
+||E2E Test||Oversee the testing and documentation of new features.|
+||Standard development||Ensure the creation or adaptation of Catena-X standards and address feedback from TC4S or other reviewers.|
 
-## Expert Group Responsibilities
+## Expert Group Roles
 
-### 1. Roadmap Preparation
+### Expert Group Leads
 
-- Prepare a roadmap for the expert group, including features, newly proposed Catena-X standards or changes to existing standards, and Keep It Together (KITs).
-- Communicate and discuss the roadmap with the assigned committee and reviewer group.
+The Leads serve as the primary points of contact, ensuring the effective delivery of the product strategy by the Expert Group. The Leads are tasked with (in addition to their role as Core Group member):
 
-### 2. Refinement and Tracking
+- **Coordination:** The Leads should maintain cohesion and coordination within the Expert Group to align with the Committee's objectives
+- **Monitoring:** Leads should monitor the Core Team member participation in the Expert Group. If they feel that a Core Team member is not performing according to their commitment, they can escalate the topic to the primary contact of thr member company (in alignment with the Committee and Association Office).
+- **Closing of the Expert Group:** Leads can request the [closing of the Expert Group](#3-closing) once the Group reached their goals.
 
-- Lead the feature refinement process for the expert group.
-- Discuss and present Git issues and standardization requests during Open Planning and lead dependency planning.
-- Track the development of features throughout the Catena-X release.
-- Regularly update the committee and reviewer group on the status during the release.
-- Update Git issues for the planned features and KIT changes in sig-release.
+### Core Group Member
 
-### 3. Project Management and Communication
+An Core Group Group Member plays an active role in shaping decisions, offering input, and collaborating with others to achieve the Expert Group goals. The experts will familiarise themselves with the implementation in Eclipse Tractus-X and the respective standards and KITs. They attend meetings, participate in discussions, and contribute to the planning and execution of tasks. An Core Group Member is responsible for taking hands-on actions by actively contributing to the development of standards, kits, and/or reference implementations.
 
-- Prepare open planning during the refinement phase.
-- Maintain regular synchronization with the committee and reviewer group during refinement.
-- Create Git issues for planned features and KIT changes in the sig-release repository with appropriate labeling (e.g., EG, prep PIx).
-- Create standardization or change requests using the Houston tool.
+Responsibilities of the Core Group members include:
 
-### 4. Quality Assurance and Presentation
+- **Voting right:** Core Group members are allowed to decide on the strategic orientation of the Expert Groups. Votes need to have a simple majority to be accepted.
+- **Actice participation in the release process:** Core members are responsible for:
+  - Defining work packages during the release planning
+  - Taking over work packages such as working on KITs and/or Standards,
+  - Ensuring that tasks are completed on time and to a high standard, and
+  - Reviewing the overall results of the Expert Group.
+- **Active contribution:** A pro-active contribution to the Expert Group is expected by providing expertise, support, and ongoing participation to help achieve the project's objectives.
+- **Time commitment:** Core Group members must commit at least 20 hours per month to the Expert Group, with additional hours being encouraged. These hours may not be evenly distributed throughout the month, as periods of higher workload should be anticipated and planned for accordingly.
+- **Stay updated:** Core Group members stay actively informed about the progress of the Expert Group by attending meetings (weeklies and workshops) and by reading the documentation (meeting minutes).
 
-- Ensure that confirmed sig-release Git issues are incorporated into feature backlogs.
-- Oversee the testing and documentation of new features.
-- Present features in the Catena-X release review.
-- Ensure the creation or adaptation of Catena-X standards and address feedback from TC4S or other reviewers.
+Each company can only be represented by one person per Expert Group. The seat in the Expert Group is tied to the individual, not to the company itself.
+Core Group members are expected to regularly reaffirm their commitment to their responsibilities. If they are unable to do so (e.g., due to internal company projects), they should proactively step down from the Core Group to ensure effective planning and allocation of available resources.
 
-### 5. Testing
+### Review Group Member
 
-- Create (in feature and also in jira/y-ray) testcases which fit to your requirements during refinement.
-- Exceute your testcases after implementaion.
-- Review the developed results and check if they fit your requirements.
+Review group members are experts in the specific field of the respective group. They serve as sparring partners to the core team, providing critical feedback, guidance, and support. To fulfill this role effectively, they must immerse themselves in the topic and closely monitor the latest progress of the expert group. Additionally, review group members may take over work packages from the core team and participate in workshops, further contributing to the group's efforts and outcomes.

docs/working-model/overview.md

@@ -3,7 +3,7 @@ sidebar_position: 1
 title: Overview
 ---
 
-This working model is meticulously designed for members of our association and those involved in the various association bodies. It serves as a comprehensive guide to understanding the organizational structure, the specific roles within the association, and the interrelation between Catena-X and Tractus-X. It includes detailed information on planning and building (Plan and Build), contrasting with the <!-- markdown-link-check-disable -->[Operating model](../operating-model/why-introduction/why-introduction.md)<!-- markdown-link-check-enable --> that describes the model for the production/live environment (Run).
+This working model is meticulously designed for members of our association and those involved in the various association bodies. It serves as a comprehensive guide to understanding the organizational structure, the specific roles within the association, and the interrelation between Catena-X and Tractus-X. It includes detailed information on planning and building (Plan and Build), contrasting with the <!-- markdown-link-check-disable -->[Operating model](/docs/next/operating-model/why-introduction)<!-- markdown-link-check-enable --> that describes the model for the production/live environment (Run).
 
 ## Audience and Purpose