Feature Overview (mandatory - Complete while in New status)
As part of the AIPCC mission to build components for all of our products, we need to work with the RHOAI team to set up wheel collections for all of their images and help them consume those using our base images.

We expect this project to take several RHOAI releases. The first step is to do the required analysis of what to images exist, which ones need to be migrated or updated, find new dependencies we are not currently building, etc. The outcome of that should be a roadmap for doing the rest of the migration.

Goals (mandatory - Complete while in New status)

RHOAI images built by the RHOAI team that include wheels use only wheels built using AIPCC tools and pipelines.

Requirements (mandatory -_ Complete while in Refinement status):
A list of specific needs, capabilities, or objectives that a Feature must deliver to satisfy the Feature. Some requirements will be flagged as MVP. If an MVP gets shifted, the Feature shifts. If a non MVP requirement slips, it does not shift the feature.

Done - Acceptance Criteria (mandatory - Complete while in Refinement status):
This work will be done when all RHOAI images are built on our base images and all RHOAI images that use wheels consume those wheels from pipelines built with AIPCC tools.

Use Cases - i.e. User Experience & Workflow: (Initial completion while in Refinement status):
Include use case diagrams, main success scenarios, alternative flow scenarios.
<your text here>

Out of Scope _{}(Initial completion while in Refinement status):{_}
High-level list of items or persona’s that are out of scope.
<your text here>

Documentation Considerations _{}(Initial completion while in Refinement status):{_}
Provide information that needs to be considered and planned so that documentation will meet customer needs. If the feature extends existing functionality, provide a link to its current documentation..
<your text here>

Questions to Answer _{}(Initial completion while in Refinement status):{_}
Include a list of refinement / architectural questions that may need to be answered before coding can begin.
<your text here>

Background and Strategic Fit (Initial completion while in Refinement status):
Provide any additional context is needed to frame the feature.
<your text here>

Customer Considerations _{}(Initial completion while in Refinement status):{_}
Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.
<your text here>

Team Sign Off (Completion while in Refinement status)

• All required Epics (known at the time) are linked to the this Feature
• All required Stories, Tasks (known at the time) for the most immediate Epics have been created and estimated
• Add - Reviewers name, Team Name
• Acceptance == Feature as “Ready” - well understood and scope is clear - Acceptance Criteria (scope) is elaborated, well defined, and understood
• Note: Only set FixVersion/s: on a Feature if the delivery team agrees they have the capacity and have committed that capability for that milestone

*An engineer or tech lead from the product requesting this feature is required for the signoff below.

• …