<Written as a user story... As a <PERSONA> trying to <ACTION> I want <THIS OUTCOME>>

Why it Matters

<help text needed>

Illustrative User Stories

<As a <USER>, I want <EASE OF ACQUISITION AND DEPLOYMENT> because <TIME TO DEPLOYMENT MATTERS TO ME>>

Expected Outcomes

<Not metrics (those are in features), but should inspire metrics>

Effect

<Effect is the expected outcome within the market. There are two outcomes; growth or retention. This represents part of the "why" statement for a feature.

Growth is the acquisition of new usage of the platform. This can be new workloads not previously able to be supported, or new end users not previously served.

Retention is maintaining and expanding existing use of the platform. This can be more effective use of tools, competitive pressures, and ease of use improvements.>

Partner

<Partner is any specific delivery vehicle requirements. These are feature components that MUST be delivered in concert with, or through, a particular BU external product. This represents part of the "how" statement for a feature. This would be the optional only category.

IHV is where a specific hardware partner must have a companion feature.

ISV is when a specific software partner has supportability requirements.

Layered product is when a Red Hat product has functional requirements. >

Additional/tangential areas for future development

Done Checklist

• Acceptance criteria are met
• Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
• User Journey automation is delivered
• Support and SRE teams are provided with enough skills to support the feature in production environment