Add "Introduction to Inclusive Research" to Platform Website/Research

shiragoodman commented 2 years ago

User Story

As a VFS team member doing research, I want to make sure my research is inclusive, so that my team can help fight sampling bias and in turn, design services that all Veterans can easily access and use.

Assignee: @CherylEvans Peer Reviewer: @briandeconinck

Description

Ticket #41709 was deprioritized due to the artifacts being outdated and in need of serious updates. However, @joshkimux shared that the Introduction to Inclusive Research guidance that he has been working on is almost ready and should be shared on the Platform Website for better VFS team visibility. In lieu of updating the outdated guidance at this time, we will instead pivot to prioritize the Introduction to Inclusive Research so that VFS teams have at least something to reference when it comes to building inclusive, non-biased research plans.

Impacted Artifacts

Introduction to Inclusive Research

Tasks

[ ] Determine where "Introduction to Inclusive Research" should live on Platform (@naomimarcussen can help)
[ ] Migrate content over to new Platform Website/research page
[ ] Validate all links. For any links the point to deprecated Github pages, locate the new guidance on Platform Website and direct there instead.
[ ] Determine if this new Introduction to Inclusive Guidance page should be linked/referenced from the Research Checklist and/or other pages on Platform Website
[ ] If you have any questions/concerns about the content, reach out to @joshkimux as he is the author
[ ] Deprecate the Introduction to Inclusive Research on gh following this guidance

Notes from @joshkimux

Notable changes include:
- updating recruitment guidance to focus on 1-2 underserved groups as primary criteria at a time to encourage lean iterative research (instead of aiming for a fully representative sample, as Clayton and I learned it makes it harder for Perigean to recruit)
- updating usability testing guidance to encourage testing with disabled Veterans first We’ve also split the trauma section from the inclusive research doc into its own document
I’m hoping we’ll have guidance and templates ready to go early 2023
Other things we’ll be working on in the coming months:
- updating the recruitment checker (which will mean returning to the introduction document to update some screenshots, don’t let that hold it back from publishing though)
- updating assistive tech research guidance
The main blocker is mostly volunteers :sweat_smile: We technically don’t have anyone explicitly responsible for doing any of these things, so the pace in which they are completed can fluctuate. I’m hoping by organizing more communities around this, we can procure more volunters.

Peer Review

To be completed by peer reviewer

[ ] User story and acceptance criteria are met

Acceptance Criteria

[ ] VFS teams are able to find inclusive research guidance on the Platform Website

How to prepare this issue

Refinement

[x] Ticket has user story, description, tasks, and acceptance criteria
[x] Ticket has additional appropriate labels, if applicable
[x] Ticket has been sized
[x] Once all above items are checked, add the 'Ready' label.
Planning

If this ticket is picked up from the Backlog mid-sprint, connect with Shira to ensure the below items are completed correctly
[x] Ticket has been discussed as a team at Planning
[x] Ticket has been assigned to appropriate initiative or quarterly epic
[x] Ticket has been assigned to a Sprint
[x] Ticket has been moved to the Planned pipeline in the Governance team board
[ ] Ticket as an assignee and peer reviewer

shiragoodman commented 1 year ago

@CherylEvans I talked to @naomimarcussen about this today at our 1:1. We agreed that it might be best to put this ticket on hold. If you have any questions, please let me know. I'm removing from the sprint and putting it on the backlog. FYI @briandeconinck

CherylEvans commented 1 year ago

Thank you Shira, understood. Cheryl

Cheryl Evans | Consultant

The So Company http://thesocompany.com/

We make the government better.

Timezone: CST | GMT - 6

@.***

SDVOSB | SBA 8(a) Certified | Digital Services Coalition Founding Member

On Wed, Nov 16, 2022 at 1:39 PM shiragoodman @.***> wrote:

@CherylEvans https://github.com/CherylEvans I talked to @naomimarcussen https://github.com/naomimarcussen about this today at our 1:1. We agreed that it might be best to put this ticket on hold. If you have any questions, please let me know. I'm removing from the sprint and putting it on the backlog. FYI @briandeconinck https://github.com/briandeconinck

— Reply to this email directly, view it on GitHub https://github.com/department-of-veterans-affairs/va.gov-team/issues/48784#issuecomment-1317571915, or unsubscribe https://github.com/notifications/unsubscribe-auth/AXSBWXA7FUDJFC3XAO673P3WIUZ6RANCNFSM6AAAAAARPD3NMU . You are receiving this because you were mentioned.Message ID: @.*** .com>

shiragoodman commented 9 months ago

@naomimarcussen this ticket was discussed at our refinement meeting in January 2024. Since Governance no longer has a researcher on our team, this is no longer relevant for us. I am removing the Governance label, however we may still want to make the recommended changes to the Research pages on Platform Website.

naomimarcussen commented 9 months ago

@sstrassberg Can you take a look at this ticket and provide your thoughts on it?

sstrassberg commented 9 months ago

@naomimarcussen I've reviewed the ticket. I think we should include this guidance on Platform website and specify that this is highly encouraged to follow but not a requirement for Collaboration Cycle.

department-of-veterans-affairs / va.gov-team