Merge branch 'main' into integration-mental-health-phone

.github/ISSUE_TEMPLATE/ap-task.md

@@ -18,7 +18,3 @@ labels: Needs refining, Accelerated Publishing
 <!-- any suppporting information, links etc. -->
 <!-- solution-specific discussion is great here. -->
 
-```[tasklist]
-### Implementation tasks
-- [ ] Use this if it helps you or feel free to delete.
-```

.github/ISSUE_TEMPLATE/cms-team-and-sitewide-crew-member-onboarding.md

@@ -121,7 +121,6 @@ You can view team sprint boards using either the Github view with Zenhub browser
 
 ### Context & History
 - [ ] How does the team fit into the larger OCTO ecosystem? [View this Mural diagram](https://app.mural.co/t/departmentofveteransaffairs9999/m/departmentofveteransaffairs9999/1686789362540/fb8f73b8d536f088e56bd3e38f0e37141560f62a?sender=u0b235d03cbd64f7f93673243)
-- [ ] Why is VA.gov using a Drupal CMS and how is our success measured? Read the [objectives and key results](https://va-gov.atlassian.net/wiki/spaces/VAGOV/pages/96698383/Product+CMS).
 - [ ] [Watch the Drupal GovCon presentation about the project](https://www.youtube.com/watch?v=WN4bGjEuQdM).
 - [ ] Why are VA Medical Centers changing their websites? Watch the [2-minute YouTube video](https://youtu.be/Xrv5wCv6cKY).
 - [ ] Why are Vet Centers important to Veterans? Watch the [2-minute YouTube video](https://www.youtube.com/watch?v=VMzkZNbKk1I).
@@ -183,7 +182,7 @@ Drupal is the VA's content management system of choice. For anyone on our team,
   - [ ] **Drupal production access**: (SOCKS or VA network required) - in DSVA #cms-support channel, use the Slack workflow to file a helpdesk support request. Ask the helpdesk to create a Drupal user for you in [prod.cms.va.gov](prod.cms.va.gov).
      * DevOps team members require an administrator account. (SOCKS or VA access with PIV card required)
      * Standard practice for other roles is to have minimal access in prod (content editor or even a blocked account) and full admin access in lower environments.
-  - [ ] [View short presentations on specific topics](https://va-gov.atlassian.net/wiki/spaces/VAGOV/pages/1714094110/CMS+Topic+Dives). Topics include site alerts, release and deploy, Facility API, etc.
+  - [ ] [View Topic Dives](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/teams/sitewide/topic-dives) (short presentations on specific topics). Topics include site alerts, release and deploy, Facility API, etc.
   - [ ] [Browse the VA Drupal CMS Knowledge Base articles](https://prod.cms.va.gov/help/).
   - [ ] What is Drupal? [Link list for Drupal context and community](https://docs.google.com/spreadsheets/d/11ppWiIggKJh-YAWia28utZXW48tJZGCEg-sFJ6eIl9c)
   - [ ] If you have a Drupal.org account, add your Agency & VA. Drupal.org > Login > My Account > Edit profile > Work tab > Add your agency, and "Department of Veterans Affairs" & save. This will help our team track Drupal open source contributions.
@@ -325,7 +324,7 @@ Each repository includes READMEs to help with setup.
  - [ ] [Platform Collab Cycle calendar](https://calendar.google.com/calendar/u/0/[email protected]&ctz=America/New_York)
 
 **CMS Collab Cycle**
-- [ ] [CMS Collab Cycle documentation](https://va-gov.atlassian.net/wiki/spaces/VAGOV/pages/1791459333/CMS+Collaboration+Flow#like-section)
+- [ ] [CMS Collab Cycle documentation](LINK TBD on CMS provision of Plat Confluence access or migration of docs to DEPO website)
 - [ ] [CMS Collab Cycle kanban board](https://github.com/department-of-veterans-affairs/va.gov-cms#workspaces/cms-collaboration-cycle-reviews-62f50368ef32b60022d76d64/board?repos=154174777)
 
 **Tracking features**

.github/ISSUE_TEMPLATE/pw-clp-request.md

@@ -25,6 +25,15 @@ Help desk ticket: <insert_help_desk_link>
 - [ ] Name of submitter (if applicable)
 Submitter: <insert_name>
 
+- Campaign title: 
+- Who the editor(s) will be for the Campaign Landing Page and any appropriate stakeholders for awareness: 
+- The goals/outcomes you are looking to achieve with the campaign: 
+- Outcome success measurement & how it will be measured (note: "Page views" is not a generally accepted success measurement): 
+- Target Audience(s): 
+-  Campaign start/end dates: 
+- Is this a seasonal campaign? 
+- If not: when campaign ends, should campaign page be archived or redirected? 
+- If redirected, where should it redirect?
 
 ## Acceptance criteria
 
@@ -43,7 +52,7 @@ Helpdesk will use #sitewide-public-websites channel to request approvals
 <insert_CLP_node_link>
 - [ ] If a new CMS editor user is needed, Helpdesk or any Drupal admin can create them and assign proper permissions according to [CLP CMS account administration policy](https://prod.cms.va.gov/help/cms-account-admin-policies/clp-cms-account-administration-policy).
 - [ ] Send the editor a link to the KB article: [self-guided Campaign Landing Page training](https://prod.cms.va.gov/help/campaign-landing-pages/how-to-manage-campaign-landing-pages)
-- [ ] Notify #sitewide-public-websites team "New CLP requested and approved" with link to this Github issue for next steps.
+- [ ] Create a post in DSVA slack channel #sitewide-public-websites, and @ mention Jill Adams and Fran Cross: "New CLP requested and approved, for your awareness:" with a link to this Github issue for next steps.
 
 
 #### Public Websites steps

.github/ISSUE_TEMPLATE/research-collab-cycle.md

@@ -0,0 +1,28 @@
+---
+name: Collaboration Cycle Research touchpoint(s) for [PRODUCT/INITIATIVE]
+about: Use this template when you have a research plan & conversation guide ready
+  for review by other teams
+title: Get through Collaboration Cycle before user research starts
+labels: UX, Research
+assignees: ''
+
+---
+
+## Description
+
+### User story
+**AS A** Researcher
+**I WANT** to go through the relevant Collaboration Cycle touchpoints before conducting user research
+**SO THAT** any design prototypes will be reviewed
+
+- Veteran-facing research must go through Platform's [Collaboration Cycle](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/)
+- Editor-facing research must go through the [CMS Collaboration Cycle](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/platform/cms/collaboration-cycle)
+
+The PM is responsible for creating the initial Collaboration Cycle ticket(s), but the Research Lead should initiate the Research touchpoint request.
+
+Note: This step is a hard blocker for Veteran-facing research, but may be less so for Editor-facing research. 
+
+## Acceptance Criteria
+- [ ] Initiated the Research touchpoint request
+- [ ] Incorporated any feedback into the Research Plan and Conversation Guide
+- [ ] Discussed any significant changes with the Sitewide UX Lead and maybe your Product Manager or Product Owner

.github/ISSUE_TEMPLATE/research-conversation-guide.md

@@ -23,17 +23,17 @@ Use the appropriate template for the group you're conducting research with:
 ## Suggested workflow/tasks:
 - [ ] Brainstorm potential tasks
 - [ ] Create initial draft of conversation guide
-- [ ] Solicit review/feedback from Sitewide UX Lead 
-- [ ] Solicit review/feedback from Product Manager (PM) and/or other team members
-- [ ] Solicit review/feedback from VA Product Owner (PO) async or in a meeting w/PM
+- [ ] Solicit review/feedback from Sitewide UX Lead
+- [ ] Solicit review/feedback from PO, PM, and/or other team members in a public slack post
+- [ ] Sitewide UX Lead provides consolidated feedback including from PO
 - [ ] Test prototype(s) with conversation guide and align
 - [ ] Post on github in project research folder for final approval before submitting to Research Review cycle
 
+
 ## Acceptance Criteria
 - [ ] Conversation guide drafted
-- [ ] Feedback incorporated from Sitewide UX Lead 
+- [ ] Feedback incorporated from Sitewide UX Lead and PO
 - [ ] Feedback incorporated from PM and/or other team members
-- [ ] Feedback incorporated from VA PO 
 - [ ] Conversation guide aligns with prototype(s)
 - [ ] Conversation guide posted on github in project research folder
-- [ ] Final approval obtained from VA PO and documented at the bottom of the file in preparation for Research Review cycle
+- [ ] Final approval obtained from Sitewide UX Lead and documented at the bottom of the file in preparation for Research Review cycle

.github/ISSUE_TEMPLATE/research-discovery.md

@@ -9,15 +9,20 @@ assignees: ''
 
 ## Description
 
-Research Discovery is a time to establish the fundamental approach for a research initiative. Possible tasks may include:
+### User story
+**AS A** Researcher
+**I WANT** to see what we know and could learn with [PRODUCT/INITIATIVE] research
+**SO THAT** we can provide value
+
+Research Discovery is a time to establish the fundamental approach for a research initiative. Potential tasks may include the following:
 
 **What do we want to know?**
-- [ ] Align with Product Manager & Product Owner on the high-level purpose and scope of the research
-- [ ] Review Product outline to understand background context
+- [ ] Align with Sitewide UX Lead, Product Manager, and Product Owner on the high-level purpose and scope of the research
+- [ ] Review Product Outline to understand background context
 - [ ] Draft big picture research questions
 
 **Has anyone else researched this before?**
-- [ ] Review previous research on this Product (if available)
+- [ ] Review previous research on this product (if available)
 - [ ] Review Research Repo for previous relevant research from other teams
 - [ ] Summarize findings from research review
 
@@ -26,7 +31,8 @@ Research Discovery is a time to establish the fundamental approach for a researc
 - [ ] Consider participants - do we have access to the right users?
 - [ ] Consider timeline - how long will this take? how much time do we have?
 
-## Acceptance Criteria
+## Possible Acceptance Criteria
+- [ ] Findings from research review are documented and shared with Sitewide UX Lead, Product Manager, and Product Owner
 - [ ] High-level scope of research is drafted and agreed upon
 - [ ] Subsequent tickets are created
 

.github/ISSUE_TEMPLATE/research-plan.md

@@ -22,20 +22,19 @@ Use the appropriate template for the group you're conducting research with:
 ## Suggested workflow/tasks:
 - [ ] Brainstorm ideas for research
 - [ ] Create initial draft of research plan
-- [ ] Solicit review/feedback from Sitewide UX Lead 
-- [ ] Solicit review/feedback from Product Manager (PM) and/or other team members
-- [ ] Solicit review/feedback from VA Product Owner (PO) async or in a meeting w/PM
+- [ ] Solicit review/feedback from Sitewide UX Lead
+- [ ] Solicit review/feedback from PO, PM, and/or other team members in a public slack post
+- [ ] Sitewide UX Lead provides consolidated feedback including from PO
 - [ ] Identify moderator(s), notetaker(s), and observer(s) if moderated research
 - [ ] Identify time slots for research sessions (twice as many slots as # of participants desired) if moderated research
 - [ ] Post on github in project research folder for final approval before submitting to Research Review cycle
 
 ## Acceptance Criteria
 - [ ] Research plan drafted
-- [ ] Feedback incorporated from Sitewide UX Lead 
+- [ ] Feedback incorporated from Sitewide UX Lead and PO
 - [ ] Feedback incorporated from PM and/or other team members
-- [ ] Feedback incorporated from VA PO 
 - [ ] Research plan posted on github in project research folder
-- [ ] Final approval obtained from VA PO and documented at the bottom of the file in preparation for Research Review cycle
+- [ ] Final approval obtained from Sitewide UX Lead and documented at the bottom of the file in preparation for Research Review cycle
 
 
 

.github/ISSUE_TEMPLATE/research-prep.md

@@ -66,15 +66,18 @@ assignees: ''
 ## For Editor-facing research
 
 **Recruitment / scheduling sessions** 
-* The Research Lead should work with Product Manager, Product Owner, and Business Stakeholders to identify a list of potential participants
+* The Research Lead should work with PM, PO, and Business Stakeholders to identify a list of potential participants
   * The pool of potential participants should be at least 2-3 times larger than the desired # of participants
+  * Consult with the CMS Platform Team on any requirements or limitations for participant recruiting
 * The Research Lead contacts and schedules participants 
   * Using their VA.gov email address or the shared [email protected] email address
   * Consider using Calendly or Microsoft Bookings to set up timeslots so participants can pick slots
   * The Research Lead should create placeholder calendar events to block those time slots and invite other team members
   * Ensure that teleconferencing rooms connected to the calendar events have correct permissions for Moderator(s)
 * The Research Lead should create placeholder calendar events to block those time slots and invite other team members 
-* Ideally one of the Observers should be a Drupal developer so that they might be there to help answer technical questions or see defects in action
+  * Identify a member of the Product Team who will serve as official Notetaker for each time slot. 
+  * Ideally one of the Observers should be a Drupal developer so that they might be there to help answer technical questions or see defects in action
+  * Coordinate with the CMS Platform team to fill additional Observer slots
 * Once participants are scheduled, the Research Lead invites other team members to official calendar events
 * The Research Lead should schedule 30-minute Daily Research Debrief meetings and invite Notetaker(s) & Observer(s)
 

.github/ISSUE_TEMPLATE/research-readout-and-post-tasks.md

@@ -0,0 +1,58 @@
+---
+name: Research Readout and Post-Research tasks
+about: Use this template when sharing your research via readouts and doing final clean-up tasks.
+title: Conduct [PRODUCT/INITIATIVE] research readout and complete post-research tasks
+labels: Research, UX
+assignees: ''
+
+---
+
+## Description
+
+### User story
+
+**AS A** researcher
+**I WANT** to wrap up my research study
+**SO THAT** I can share insights with others and protect participants' private information
+
+## Tasks
+
+**Collaborate**
+
+- [ ] Share draft research report with team and ask for feedback
+- [ ] Incorporate feedback into report
+- [ ] Discuss draft recommendations with team 
+
+  - Recommendations are key outputs of the research process. They connect your findings back to the product roadmap(s) and shape the experience of future users. Depending on the type of research conducted, recommendations might be narrowly focused on improving a specific interface component of your team's product, or they might have broad implications for multiple parts of the VA.gov ecosystem. Work with the Sitewide UX Lead, UX team, Product Manager, and Product Owner to generate, refine, and categorize recommendations. PMs and POs also play a key role in socializing recommendations to other teams.
+
+- [ ] Work with Sitewide UX Lead, PM, and/or PO to discuss whether research readout(s) are needed. If so, determine audience and meeting length (e.g., 30-min meeting with 20-min presentation and 10-min discussion).
+- [ ] Work with PM to schedule research readout(s)
+
+
+**Research Readout(s)**
+- [ ] Draft readout presentation slides
+- [ ] Share readout slides with Sitewide UX Lead for feedback
+- [ ] Incorporate feedback from Sitewide UX Lead
+- [ ] *(optional)* Consider doing a practice runthrough to gauge flow and length
+- [ ] Present readout(s) to team and/or stakeholders
+- [ ] Revise report and/or readout slides per feedback from readout(s)
+- [ ] *(optional)* Consider presenting at Sprint Demo; make a *very short* version of your readout slides
+- [ ] *(optional)* Consider presenting at Veteran Digital User Experience Weekly Design Sync meeting; slack Naomi Marcussen to schedule a date; [presentation template here](https://docs.google.com/presentation/d/13G80avWGdY7tHU40PbP_l05W1yRpDr-opOk0u_AAhzQ/edit#slide=id.g892adcb623_0_141)
+
+
+**Add Findings to Research Repository**
+- Once your report is final, link to the relevant research repository:
+  - Veteran-facing research: [How to add research to Research Repo](https://github.com/department-of-veterans-affairs/va.gov-research-repository/issues/70) > *What to do when you complete your research*
+  - Editor-facing research: [CMS Research Repository](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/platform/cms/research)
+
+**Delete and Archive Research Materials**
+- Review your notes and synthesis materials to make sure they don't contain any PII ([Personally Identifiable Information](https://depo-platform-documentation.scrollhelp.site/research-design/what-is-pii)). Then add them to your github research folder, and link to them in your research report.
+- Once your readouts are complete, you should delete [session recordings](https://depo-platform-documentation.scrollhelp.site/research-design/recording-user-research-sessions) and transcripts from your computer and empty the trash folder.
+
+
+## Acceptance Criteria
+- [ ] Feedback incorporated into research report
+- [ ] Readout(s) conducted
+- [ ] Findings added to Research Repo
+- [ ] Notes and synthesis materials scrubbed of PII, posted to github, and linked to report
+- [ ] Session recordings and transcripts deleted from your computer