diff options
Diffstat (limited to 'doc/development/contributing/design.md')
-rw-r--r-- | doc/development/contributing/design.md | 8 |
1 files changed, 6 insertions, 2 deletions
diff --git a/doc/development/contributing/design.md b/doc/development/contributing/design.md index 8426db84aa4..352392931c0 100644 --- a/doc/development/contributing/design.md +++ b/doc/development/contributing/design.md @@ -9,7 +9,11 @@ To better understand the priority by which UX tackles issues, see the [UX sectio Once an issue has been worked on and is ready for development, a UXer removes the ~"UX" label and applies the ~"UX ready" label to that issue. -There is a special type label called ~"product discovery". It represents a discovery issue intended for UX, PM, FE, and BE to discuss the problem and potential solutions. The final output for this issue could be a doc of requirements, a design artifact, or even a prototype. The solution will be developed in a subsequent milestone. +There is a special type label called ~"product discovery" intended for UX, +PM, FE, and BE. It represents a discovery issue to discuss the problem and +potential solutions. The final output for this issue could be a doc of +requirements, a design artifact, or even a prototype. The solution will be +developed in a subsequent milestone. ~"product discovery" issues are like any other issue and should contain a milestone label, ~"Deliverable" or ~"Stretch", when scheduled in the current milestone. @@ -17,7 +21,7 @@ The initial issue should be about the problem we are solving. If a separate [pro is needed for additional research and design work, it will be created by a PM or UX person. Assign the ~UX, ~"product discovery" and ~"Deliverable" labels, add a milestone and use a title that makes it clear that the scheduled issue is product discovery -(e.g. `Product discovery for XYZ`). +(for example, `Product discovery for XYZ`). In order to complete a product discovery issue in a release, you must complete the following: |