-
Feature
-
Resolution: Unresolved
-
Minor
-
None
-
None
Feature Overview (aka. Goal Summary)
An elevator pitch (value statement) that describes the Feature in a clear,
concise way.
As part of offering a well localized experience to our customers, we should see if there are options at hand to help us localize log messages to help customers diagnose and troubleshoot their system. This setting could be system-wide setting, and doesn't need to extend down to per user. Knowing how easy or hard this would be will inform future discussions on if it can be pulled into a future release.
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.
- Investigate how this could be achieved and write up a findings doc or produce a prototype showing a potential way to handle this.
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.
- Assess feasibility of this, looking into available tools to support this
- Write up and attach findings or any exploratory code that's worth sharing
- Prior to closing the feature, discuss with PM if we need a followup feature to capture next stepsĀ
Out of Scope (Optional)
High-level list of items that are out of scope.
- Formally translating logs into supported languages. This is a PoC investigation.
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>