Update dev-issue-template.md (#3186)

* Update dev-issue-template.md

* Update dev-issue-template.md

* Update .github/ISSUE_TEMPLATE/dev-issue-template.md

Co-authored-by: Andrew <84722778+andrew-jameson@users.noreply.github.com>

* Update .github/ISSUE_TEMPLATE/dev-issue-template.md

Co-authored-by: Andrew <84722778+andrew-jameson@users.noreply.github.com>

* Update team-meetings.md

---------

Co-authored-by: Andrew <84722778+andrew-jameson@users.noreply.github.com>

.github/ISSUE_TEMPLATE/dev-issue-template.md

@@ -9,6 +9,7 @@ assignees: ''
 
 **Description:**
 _Provide a brief background and justification for this issue_
+_OFA & UX team: Please include bullets capturing the value to STT end users, related guidance, and/or talking points that should be communicated to STTs in release notes_
 
 
 **Acceptance Criteria:** 

docs/How-We-Work/team-meetings.md

@@ -68,12 +68,12 @@ A typical sprint schedule is described in the table below.
       - External factors outside of the author spending time building the ticket (ie need external team's input, see how a feature develops, etc.)
       - Ex. Waiting on X ticket to finish the scope of said unrefined ticket, problem found / unsure how big it is and knows other work will unearth it
       - If we know the ACs but not the tasks, then its unrefined
+      - Release Notes summary is empty or incomplete as applicable, to be provided by UX/Product by default.
    - Refined: Ticket is complete and is ready to be executed.
    - Refined & Ready to Go (Next Sprint)
       - "Earmarked" work for the upcoming sprint.
 - **Labelling:**
    - WIP
-      - Author knows the 5 W's or darn near (90%) 
       - Drafted ticket – either still on the author the finish their part or a short team conversation is needed. 
       - Administrative in nature
       - Ex. Stub, ticket that doesn't feel there's enough to warrant an introduction