Goal Summary:

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

Customers want to enforce safe image practices, but they have no control of what was done in the base image. Currently the base image can both mask poor practices as well as add false violations as can be seen in these two examples:

1. (MASK) USER directive : The base image may have a root user directive (which might be root in fact) so our policy does not catch the case that the higher level is missing the USER directive, and the image results in running as root
2. (FALSE POSITIVE) COPY command should be used instead of ADD: The base image  might use ADD, so even if all the higher  layers use COPY, this would still be flagged as a violation.

Goals and expected user outcomes:

The observable functionality that the user now has as a result of receiving this feature. Include the anticipated primary user type/persona and which existing features, if any, will be expanded. Complete during New status.

<your text here>

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>