Feature Overview (aka. Goal Summary)  

An elevator pitch (value statement) that describes the Feature in a clear, concise way.  Complete during New status.

We have been releasing a new version of TF regularly and we should continue to do that for 2Q24.

Goals (aka. expected user outcomes)

The observable functionality that the user now has as a result of receiving this feature. Complete during New status.

Expectation is that we continue to release TF regularly throughout 2Q24.

Requirements (aka. Acceptance Criteria):

A list of specific needs or objectives that a feature must deliver in order to be considered complete. Be sure to include nonfunctional requirements such as security, reliability, performance, maintainability, scalability, usability, etc. Initial completion during Refinement status.

Supported Clients	Option
Supported in ROSA cli	( ) Yes ( ) No N/A
Supported in OCM cli	( ) Yes ( ) No N/A
Supported in OCM UI	( ) Yes ( ) No N/A
Supported in TF	Yes ( ) No ( ) N/A
Supported in Capi	( ) Yes ( ) No N/A
Supported Offerings	Option
Fedramp supported?	Yes ( ) No ( ) N/A
OCP Support	Option
Is it already supported in OCP?	( ) Yes ( ) No N/A

For each release, we are expected to go through the following process:

• create release candidates (rc)
• go through regression tests
• triage and fix issues found during regression testing
• smoke / sanity tests final rc candidate (if needed)
• go through release process (TBD)
• sanity check by downloading new TF from production

Use Cases (Optional):

Include use case diagrams, main success scenarios, alternative flow scenarios.  Initial completion during Refinement status.

N/A

Questions to Answer (Optional):

Include a list of refinement / architectural questions that may need to be answered before coding can begin.  Initial completion during Refinement status.

Out of Scope

High-level list of items that are out of scope.  Initial completion during Refinement status.

N/A

Background

Provide any additional context is needed to frame the feature.  Initial completion during Refinement status.

N/A

Customer Considerations

Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.  Initial completion during Refinement status.

Customers get to access new features as we continue to release new features, 

Documentation Considerations

Provide information that needs to be considered and planned so that documentation will meet customer needs.  Initial completion during Refinement status.

We don't generate any doc with each ROSA CLI unless there is anything that specifically requires it.

Interoperability Considerations

Which other projects and versions in our portfolio does this feature impact?  What interoperability test scenarios should be factored by the layered products?  Initial completion during Refinement status.

N/A