Commit 343534f4 authored by Mike Lewis's avatar Mike Lewis

Updates to Feature proposal.md

parent b2c6058a
### Problem to solve ### Problem to solve
<!--- What problem do we solve? --> <!-- What problem do we solve? -->
### Target audience ### Target audience
...@@ -9,21 +9,28 @@ or define a specific company role. e.a. "Release Manager" or "Security Analyst" ...@@ -9,21 +9,28 @@ or define a specific company role. e.a. "Release Manager" or "Security Analyst"
### Further details ### Further details
<!--- Include use cases, benefits, and/or goals (contributes to our vision?) --> <!-- Include use cases, benefits, and/or goals (contributes to our vision?) -->
### Proposal ### Proposal
<!--- How are we going to solve the problem? --> <!-- How are we going to solve the problem? -->
### Documentation ### Documentation
<!-- What doc pages need to be created or updated across user, admin, and API docs? <!--
What concepts, procedures, or info is needed on each? * What doc pages need to be created or updated across user, admin, and API docs?
PMs: Specify feature name, description, benefits, and use cases, if applicable. --> * What concepts, procedures, or information is needed in each area? Is there an 'old way' or workaround to deprecate?
Product managers:
* By the kickoff, finalize the answers to the bullets above, and:
* If applicable, specify new or updated feature name(s), description(s), benefits,
and use cases, which may all be used in the documentation or features.yml.
* Specify which use cases or scenarios would benefit from a set of instructions
or a guide unique to that use case. -->
### What does success look like, and how can we measure that? ### What does success look like, and how can we measure that?
<!--- If no way to measure success, link to an issue that will implement a way to measure this --> <!-- If no way to measure success, link to an issue that will implement a way to measure this -->
### Links / references ### Links / references
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment