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 an all-in-one RHOSO cloud with minimal footprint and prescriptive configuration, for testing and POC purposes but also that I can expand to a production-ready environment later on.

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?

This is a docs-only feature based on existing deployment procedures and components. Customers and field roles that are performing POCs or testing RHOSO as a product will be able to use this quickstart guide to deploy a minimal environment for testing and future productizations as needed.

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 performing the quickstart deployment.

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 considerations (TBD)

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

Full production-ready airgapped/disconnected environment (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.

Quickstart deployments have been a part of the director-based RHOSP in the past, but due to the size and complexity of the product they became obsolete and were deprecated (i.e. all-in-one packstack clouds). This quickstart guide is similar to the dev preview guides in that it answers a need for a minimal deployment that looks and acts the part of RHOSO, that customers and partner/field roles can use to demonstrate and get started on a testing environment quickly.

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