Goal Summary:

Reduce the risk of significant performance and scalability regressions by implementing automated tests to detect regressions prior to release.

Goals and expected user outcomes:

• Engineers will be blocked from merging their PR if a significant performance regression is detected.
• This will reduce the likelihood of customers experiencing performance regressions, which can cause significant frustration for the customer and reputational harm for Red Hat.  It's also likely much more expensive to address after release than before.

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.

<enter general Feature acceptance here>

Success Criteria or KPIs measured:

A list of specific, measurable criteria that will be used to determine if the feature is successful. Include key performance indicators (KPIs) or other metrics., etc. Initial completion during Refinement status.

<enter success criteria and/or KPIs here>

Use Cases (Optional):

Include use case diagrams, main success scenarios, alternative flow scenarios together with user type/persona. Initial completion during Refinement status.

<your text here>

Out of Scope (Optional):

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

<your text here>