Feature Overview (mandatory - Complete while in New status)
An elevator pitch (value statement) that describes the Feature in a clear, concise way. ie: Executive Summary of the user goal or problem that is being solved, why does this matter to the user? The “What & Why”... 

As a RHOSO administrator, I would like to deploy RHOSO in an airgapped/disconnected environments or in any environment but using only the CLI workflow.

Goals (mandatory - Complete while in New status)
Provide high-level goal statement, providing user context and expected user outcome(s) for this Feature

• Who benefits from this Feature, and how? 
• What is the difference between today’s current state and a world with this Feature?

The code for supporting this workflow is already available, this feature tracks the documentation and testing of the end-to-end process in a customer-emulated environment.

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):
Acceptance Criteria articulates and defines the value proposition - what is required to meet the goal and intent of this Feature. The Acceptance Criteria provides a detailed definition of scope and the expected outcomes - from a users point of view

Tested and fully supported documentation for users to be able to follow while deploying with CLI in disconnected environments.

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

• Greenfield airgapped/disconnected deployment
• Greenfield CLI-only deployment
• Updates/upgrades (TBD)

Out of Scope __(Initial completion while in Refinement status):
High-level list of items or persona’s that are out of scope.

Quickstart procedures (tracked in a separate ticket, created from the same spike)

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..

Documentation is the main deliverable unless engineering work is discovered during refinement or authoring

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

Airgapped/disconnected environments are a supported long-term use-case with most customers of a certain cloud size having security/privacy requirements that necessitate offline deployment. Other customers might need to automate spinning up operator deployment and therefore need CLI support.

Customer Considerations __(Initial completion while in Refinement status):
Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.

Primary requester/field contact for questions is rhn-support-knoha 

Team Sign Off (Completion while in Planning 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