Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Business Partner KIT Release 23.12 Miscellaneous Acceptance Criteria #196

Closed
4 tasks done
kelaja opened this issue Oct 6, 2023 · 4 comments
Closed
4 tasks done
Assignees
Labels
business partner Feature/Bug for Business Partner KIT kit RM KIT definition
Milestone

Comments

@kelaja
Copy link
Contributor

kelaja commented Oct 6, 2023

Release 23.12 Miscellaneous

  • Version under Review

    • Pull request for KIT version under review must be placed minimum one week prior to your reserved Quality-Gate timeslot (to enable formal reviews by relevant BOs, BDAs, DevSecOps System Team)
    • Prerequisite: IP approval by all companies is available!

    Artifact Repository:

    • Eclipse Tractus-X repo of KIT

    Contacts:

    • Responsible: PO
    • Review by:
      • T-X Committer / Project Lead
      • DevSecOps System Team
  • Approval of Acceptance Criteria

    • Product Manager / Business Owner confirms:
      • All acceptance criteria met (as defined in PI documentation). Relevant evidence is available.

    Best Practice:

    • PO / PCA to obtain BO / BDM OR PM / SA approval prior to Gate review.

    Artifact Repository:

    Contacts:

    • Responsible: PO/PCA
    • Consult: KIT-CONTACT1, KIT-CONTACT2
    • Review by: BO / BDM (from relevant Domain) OR PM / SA
  • Test and Approval of Developer Journey

    • recommended; not mandatory
    • Business Owner / Product Owner should conduct a case study with at least 1 provider (ideally outside) of the consortium to test the developer journey.

    Best Practice:

    • PO / BO to obtain feedback from case studies prior to Gate review.

    Artifact Repository:

    • Case Study

    Contacts:

    • Responsible: PO/BDA
    • Consult: KIT-CONTACT1, KIT-CONTACT2
    • Review by: Case Study Team
  • Provide change log page in KIT

    • Each KIT team must provide a KIT-specific release note/change log for developers

    Best Practice:

    Artifact Repository:

    • Provide change log page in KIT - example

    Contacts:

    • Responsible: PO/BDA
    • Review by: Release Management
@kelaja kelaja added the kit RM KIT definition label Oct 6, 2023
@kelaja kelaja added this to the 23.12 milestone Oct 6, 2023
@kelaja kelaja self-assigned this Oct 6, 2023
@RolaH1t RolaH1t added the business partner Feature/Bug for Business Partner KIT label Oct 10, 2023
@maximilianong maximilianong added Prep-PI12 CX-ART PI Preparation Issues for Consortia Planning kit RM KIT definition business partner Feature/Bug for Business Partner KIT and removed kit RM KIT definition business partner Feature/Bug for Business Partner KIT Prep-PI12 CX-ART PI Preparation Issues for Consortia Planning labels Nov 2, 2023
@HeyHardy
Copy link

the actual version with all acceptance criterias is available here https://eclipse-tractusx.github.io/docs-kits/next/kits/Business%20Partner%20Kit/Adoption%20View

@kelaja
Copy link
Contributor Author

kelaja commented Nov 22, 2023

  • BO and PO Approval Provided
  • all points of the Adoption View are accepted @maximilianong

@alexKeppler
Copy link

BPDM KIT is approved by BO

@HeyHardy
Copy link

@kelaja kelaja closed this as completed Jan 31, 2024
@github-project-automation github-project-automation bot moved this from Inbox to Done in Release Planning Jan 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
business partner Feature/Bug for Business Partner KIT kit RM KIT definition
Projects
Status: Done
Development

No branches or pull requests

6 participants