jjeroch
commented
6 months ago Attention @rybtim : Upcoming PI Planning Preparation
As we gear up for the forthcoming PI Planning session, it is crucial that all features under consideration align with our established Feature Quality Standards and Definition of Done (DoD) guidelines. To ensure your feature is thoroughly prepared and stands a strong chance of being prioritized, please provide comprehensive documentation that includes the following components:
- Feature Summary: An executive overview that encapsulates the essence and objectives of the feature.
- Change Description:
- High-Level Overview: A succinct synopsis of the proposed changes and their overarching impact.
- Detailed Analysis: An in-depth exploration of the specific alterations, including a clear exposition of the anticipated impact on existing systems.
- Impacted Components: A list identifying all system components that will be affected by the feature implementation, accompanied by a brief explanation of the nature of the impact.
- Acceptance Criteria: A set of clearly defined conditions that must be met for the feature to be considered complete and acceptable.
- Test Scenarios: A detailed outline of test cases that cover all functional paths of the feature to ensure robust validation and verification.
- Risks/Dependencies
Please note that any feature submissions lacking these essential elements will not be eligible for consideration in the upcoming PI Planning. It is imperative that your documentation is both thorough and precise to facilitate a smooth and effective planning process.
Please let me know in case you have any questions
Grand-Thibault
rybtim
stephanbcbauer
Sebastian-Wurm
Description
Current legal form list is not sufficient for the first Go-Live of sharing members. GLEIF list does not reflect all countries worldwide. Analysis must be done which countries are missing and which ones, out of them, are required to be reflected with the country specific legal forms in this list.
Recommended to align with the "roll out plan" EU first.
Pool / Gate data model and APIs MUST be adapted to include a way for downloading the legal forms accepted by Catena-X and valid for each country. It MUST be ensured in the sharing process, that only those legal forms are used in the business partners. Legal form list MUST be included as annex in the Pool and Gate API standardization documents, so that it is clear which legal forms are accepted by Catena-X. Portal onboarding and own company data maintenance UIs COULD present this list as a drop-down to select the correct legal form for the business partner.
Impact
Additional information