Skip to main content
Release: Jupiter (preview)

Release Planning Days

Task​

[!TIP] A two-day PI Planning workshop to align the upcoming development activities.
Principle: People who do the work plan the work.

During the Open Planning the items for upcoming release are planned. All feature proposals that were handed in on time are going to be presented to the audience. The Open Planning is the last chance to provide feedback about the scope of the feature proposal. After the presentation of the feature proposal by the feature author, the committers are going to prioritize the feature proposal in alignment with the topic owner. A feature proposal becomes part of the upcoming release only by receiving the commitment by the committees and not by being presented in the Open Planning!

To enter the Open Planning a feature proposal must meet the DoE X days before the Open Planning (Cut-Off)! Feature proposal that meet the DoE after the Cut-Off won't be considered in the Open Planning. This means it will likely be deferred to a future release.

Schedule​

Day 1Day 2
Part I - Open Planning\ (public)- Vision & Intro (30 min)\ - Vision Deep Dive Tractus-X (30 min)\ - Joint Open Planning (150 min)\ - Open Planning Wrap-up Day 1- Draft Plan Review (60 min)\ - Joint Open Planning (90 min)\ - Release YY.MM Confidence vote (30 min)\ - Feedback/Retro (30 min)\ - Open Planning Wrap Up (30 min)
Part II - Standards Planning\ (association internal)- Vision Deep Dive C-X Standards (30 min)\ - Standards Planning (180 min)\ - Standards Planning Wrap up- Final Plan Review\ - Release YY.MM Confidence vote (30 min)\ - Feedback/Retro (30 min)\ - Management Review (C-X association mgmt. only)

Outcome​

  • Have a clear plan for the Development & Release Phase.
  • Backlog is prioritized & split into six Product Increments (2 weeks Dev. work including unit test & Integration testing for each).
  • Prioritized backlog: Decision by committer group Committed, prioritized backlog for the next release.
  • Resource commitment: Teams and individuals commit to the work they will deliver, fostering accountability and setting clear expectations for the upcoming release.
  • Updated roadmap: The project's roadmap is updated to reflect the decisions made during the release planning, providing transparency to stakeholders and the community. [TO-DO clarify location of the roadmap / where will this be published]
  • Decisions are documented: All decisions and commitments made during the planning are documented in the decision board or directly in the comment section of a feature. [TO-DO link to the architecture decision board]
  • Communication plan: After the planning a communication via mailing-list will be done by the project lead including the relevant links and decisions.

Attendees​

  • Expert Groups
  • Committees
  • Tractus-X community (contributor/committer)

Timeline​

  • 2 days