Feature Overview (aka. Goal Summary)

(Description: An elevator pitch (value statement) that describes the Feature in a clear, concise way. )

Goals (aka. expected user outcomes)

(Description: 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. )

Requirements (aka. Acceptance Criteria):

(Description: 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. )

Use Cases (Optional):

Include use case diagrams, main success scenarios, alternative flow scenarios. Initial completion during Refinement status.

Questions to Answer (Optional):

Include a list of refinement / architectural questions that may need to be answered before coding can begin. Initial completion during Refinement status.

Out of Scope

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


h3. Background

(Description: Provide any additional context is needed to frame the feature. Initial completion during Refinement status.)

Customer Considerations

(Description: Provide any additional customer-specific considerations that must be made when designing and delivering the Feature. )

Documentation Considerations

(Description: 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. )

Interoperability Considerations

(Description: Which other projects, including ROSA/OSD/ARO, and versions in our portfolio does this feature impact? What interoperability test scenarios should be factored by the layered products? )