Feature Overview (aka. Goal Summary)

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

Need to decide what the next phase should include. We have some related requests to consider, ideas from last phase, and other areas we could expand on. Requirements TBD.

Goals (aka. 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. 

• Engineering Manager / Security Team: I want to see high-level roll-up metrics like the total count of critical security vulnerabilities (CVEs) or major bugs across my portfolio, so I can prioritize resource allocation and identify teams/areas requiring immediate attention. (moved from RHDHPLAN-311)
  • Add support for more data sources
• Improvements to data accessibility and verification
  • Add a timestamp to the cards to show when the data was last refreshed
    • Could a scheduler be triggered to run on demand (eg from a button click)?
  • Should we improve the backend architecture to allow users to either click through from the scorecard to go see the data in the system we're pulling from, or see if there's a generic way we could provide more details and show additional context in RHDH?
• Improved configuration
  • Should categories become more configurable?
  • User replaceable descriptions/titles?
  • UI flow for creating/modifying KPIs and cards?
• New card types
• Review related feature requests and assess priority to see if anything needs to be included

Requirements (aka. Acceptance Criteria):

A list of specific needs or objectives that a feature must deliver in order
to be considered complete. If the feature spans across releases then good
to have scope for each release with acceptance criteria. Be sure to
include nonfunctional requirements such as security, reliability,
performance, maintainability, scalability, usability, etc.

<enter general Feature acceptance here>

Out of Scope (Optional)

High-level list of items that are out of scope.

<your text here>

Customer Considerations (Optional)

Provide any additional customer-specific considerations that must be made
when designing and delivering the Feature. Initial completion during
Refinement status.

<your text here>

Documentation Considerations

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.

<your text here>