Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TWE: Create Template Issue: Create or update research roadmap details #450

Open
25 of 31 tasks
pandanista opened this issue Jul 18, 2023 · 14 comments
Open
25 of 31 tasks
Labels
complexity: medium feature: research All issues involving research feature: roadmap feature: template creation (step 1) issue to create a new template (see other labels with test in them) feature: template Participant Type: All role: UX research lead size: 1pt Can be done in 6 hours

Comments

@pandanista
Copy link
Member

pandanista commented Jul 18, 2023

Dependencies

Overview

We need to create a template issue for creating TWE: Research: Research Roadmap: Create or update (named in the format as TWE: Role: Direct Object: Action Verb) so that we have a consistent, transparent, defined, and self-supporting structure for people creating them.

Resources/Instructions: This section is at the bottom of this issue (scroll to the bottom to view it now). You will be asked to add links to this section while completing the issue.

Action Items

Customize this issue

  • Customize this issue by adding the Name of Issue Template.
    • Note: An issue template's name is different from the issue title created from the template.
    • Search for TWE: Research: Research Roadmap: Create or update by using the browser search (Mac: ⌘+F; PC: Ctrl+F)
    • Replace the keyword string (including text and the brackets) below with the name of your issue template according to the template naming convention: TWE: Role: Direct object: Action verb
      • The role is the primary owner of the issue template (e.g., Research, Design, Product)
      • Direct object should be the item that we're updating or working on (e.g., Wiki, Interviews, Roadmap)
      • Action verb should be the main descriptor of the action items (e.g., Update, Create, Transcribe)

Customize the issue settings (located in right sidebar)

Change the issue settings to ensure the issue is properly categorized and easy to manage.

  • Under Assignees, assign yourself.
  • Under Projects, choose gear, choose Repository, and choose TWE Project Management.
  • Add the milestone: Project Management
  • Add a feature label specific to what the template is related to, if available. If not clear what you should use, ask product.

Customize template draft

Create a draft of new template, which will be known as our "draft".

  • Copy resource 1.01 Content to copy for draft to a new comment on this issue.
  • In your draft, fill out the top part (called front matter) with the following information. See resource 1.02 Front Matter Resources section below for definitions and examples.
    • Name
    • About
    • Title
    • Labels
  • Define any Dependencies (or remove the dependency section if there is no dependency)
  • Customize the Overview section
  • Fill out the Action Items section (in your draft) by defining the steps that are required to be done, keeping the following in mind:
    • The person working on this issue might be new to the org, so the issue should be able to be worked on without any prior knowledge
    • If the person needs to add links, or put documents in specific locations, the place where they can do that action must be linked in the resources section
      • The links in the resources section provided by the issue creator should be in the same order as the Action Items
      • Refer to resource 1.03 Example Action Items for Finding Wiki Page and Template for an example of how to write clear instructions that avoid compound steps (steps within a step).
    • Number each resource in the order each resource appears in the Action Items
      • Group resources into numbers and decimals (e.g., Resource 1.01, Resource 2.01)
      • Group the resources based on whether they are available when making the issues or they need to be created from this issue
        • If the resource is available, then group it under the Resources for creating this issue section (e.g., Resource 1.01, Resource 1.02, Resource 1.03)
        • If the resource will be delivered or created from this issue, then group it under the Resource links gathered during the making of this issue (e.g., Resource 2.01, Resource 2.02, Resource 2.03)
  • If documents or folders (sheets, docs, presentations, dashboard, etc.) will be created, find the document template that should be used by checking resource 1.04 WIKI Templates by role pages.
    • If there is a template
      • Add a link to the template into the #### Resources for creating this issue section of your draft
    • If there is no template yet
      • Put a placeholder into the #### Resources for creating this issue section of the draft [TWE: Template Issue: Research: [Replace ACTION VERB][Replace DIRECT OBJECT]
  • Get sign-off by Product on the draft
  • Create the template issue on the repo
  • Add the link to the new issue template once created to resource 2.01. Find by clicking on the Getting started button to the right of the new template listed on new issue page
  • Update the appropriate place in the wiki for your template (see resources section)

Resources/Instructions

Resources for creating this issue

1.01 Content to copy for draft

Draft of template issue for `TWE: Role: Consent Documents for Participants Over 18: Create`
---
**name:** TWE: Template Issue: Research: [Replace ACTION VERB][Replace DIRECT OBJECT]
**about:** We are creating a template to complete `TWE: Role: Consent Documents for Participants Over 18: Create` issue so we can stay consistent in our process
**title:** TWE: Research: IS[Replace YY]: RP[Replace 000]: [Replace TYPE OF PARTICIPANT] [Replace TYPE OF RESEARCH METHOD]: [Replace DIRECT OBJECT]: [Replace ACTION VERB]
**labels:** 'feature: research', 'feature: missing', 'size: missing', 'Participant Type: missing', 'Research 000: missing', 'role:  UI/UX research', 'milestone: missing', 'complexity: missing'
**assignees:** 

---
#### Instructions for creating this issue
The person who creates this issue should use these links to add links to the resources section and customize this issue
- Customize the issue
    - [ ] Replace the keyword strings (including text and the brackets) below with the appropriate values by using the browser search (Mac: Command+F PC: Ctrl+F)
    - [ ] Search for `[Replace`
    - [ ] Replace with whatever the keyword or information is asking for.
- Customize the issue settings (located in right sidebar)
    - [ ] Under Labels, add labels for any labels identified as missing
    - [ ] Remove the corresponding missing labels
    - [ ] Under Projects, choose gear, choose "Repository," and choose TWE Project Management.
    - [ ] Add the milestone: [Replace MILESTONE]
    - [ ] Add a feature label specific to what the template is related to, if available. If not clear what you should use, ask product.
- Customize dependencies 
    - [ ] If no dependencies, delete dependency section
    - [ ] If dependencies, add the dependencies (any issue or reason that would prevent the action items from being completed)
- Remove this section.
    - [ ] Delete this section when all the checkboxes above are complete (i.e., the issue assignee will never see this part)

### Dependencies

### Overview
We need to [Replace ACTION VERB] [Replace DIRECT OBJECT] for [Replace REASON].

### Action Items
A STEP BY STEP LIST OF ALL THE TASK ITEMS THAT YOU CAN THINK OF NOW EXAMPLES INCLUDE: Research, reporting, etc.

### Resources
#### Resources for creating this issue
1.01
1.02

#### Resources gathered during the completion of this issue
2.01
2.02

1.02 Front Matter Resources

1.02.01 Front Matter Fields and Meaning
  • name: (name that appear on the new issue tab)
  • about: (is the description that appears next to the issue template on the new issue tab)
  • title: (the title that appears when the issue is created. User then customizes this title for their issue)
    • Use the naming convention: TWE: Role: Direct object: Action verb
    • If more than one word should go into the direct object spot, use multiple square brackets with the keyword (see example)
  • labels: (choose the labels that will be the same each time, and choose missing labels for the ones that depend on content)
  • assignees:
1.02.02 Front Matter Field example
  • name: 'TWE: Template Issue: Research: Create Roadmap'
  • about: We are creating a template to complete TWE: Role: Consent Documents for Participants Over 18: Create issue so we can stay consistent in our process
  • title: 'TWE: Research: IS[Replace YY]: RP[Replace 000]: [Replace TYPE OF PARTICIPANT] [Replace TYPE OF RESEARCH METHOD]: Roadmap : Create'
  • labels: 'feature: research', 'feature: roadmap', 'milestone: missing', 'role: UI/UX research', 'Participant Type: missing', 'Research 000: missing', 'complexity: missing'
  • 'size: 0.50pt'
  • assignees: ''

1.03 Example Action Items for Finding Wiki Page and Template

1.03.01 Example Action Items
### Action Items
- Customize wiki page
     - [ ] Go to link 1.01 Internship Wiki, Join the team page
     - [ ] Find wiki page for this issue by looking at role pages.
     - [ ] Copy the link for the wiki page.
     - [ ] Add the link to Resource 2.01
        - [ ] Add the name of the link in square brackets
        - [ ] Add the URL in parenthesis without a space between the square bracket and parenthesis
- Customize document template.
    - [ ] Go to link 1.02 Design Process Overview
    - [ ] Find document template that should be used in this issue.
    - [ ] Copy the link for the template.
    - [ ] Add the link to Resource 2.02
        - [ ] Add the name of the link in square brackets
        - [ ] Add the URL in parenthesis without a space between the square bracket and parenthesis
1.03.02 Example Resource Lists
### Resources for creating this issue
1.01. [Internship Wiki, Join the team page](https://github.com/hackforla/internship/wiki/Joining-the-Team)
1.02. [Design Process Overview](https://github.com/hackforla/internship/wiki/Design-Process-Overview)

### Resource links gathered during the making of this issue
2.01. [Wiki page for [Replace TYPE OF ROLE]]
2.02. [TWE: Template: [Replace NAME OF TEMPLATE]]

Resources gathered during the completion of this issue

@pandanista
Copy link
Member Author

pandanista commented Jul 18, 2023

Research Roadmap Update/Creation Template


name: TWE: Template Issue: Research: Create or Update Research Roadmap Details
about: This issue helps you structure your template issue to be consistent with our other template issues in research roadmap creation or updates
title: TWE: Research: RP[Replace 000]: [Replace TYPE OF PARTICIPANT] Research Roadmap: Create/Update
labels: 'feature: research', 'feature: research roadmap', 'Participant Type: missing', 'Research 000: missing', 'size: 1pt', 'role: UI/UX research', 'milestone: missing', 'complexity: medium'
assignees: ' '


Instructions for creating this issue

The person who creates this issue should use links in the section "Resources for creating this issue" (i.e., 1.01, 1.02, etc.) to customize this issue.

  • Customize the issue
    • Open the "Research Overview" wiki page (Resource 1.01)
    • Choose the appropriate research roadmap or research plan folder (ie., RP###) on the wiki page
    • Use the information on the wiki page and in research roadmaps or research plans to customize this issue
    • Copy and paste entire template text in this issue into text editor (ie., "TextEdit" on Mac, "Wordpad" on PC)
    • Use Find/Replace (Mac: ⌘+F or PC: Ctrl+F) to search for and replace the keyword strings (including text and the brackets) below with the appropriate values
      • Year
        • Find/Replace [Replace YY] with research year (Two digit format, ex: "22" for year "2022"; if the research hasn't been conducted, use the next cohort's enrollment year)
      • Research Plan Number
        • Find/Replace [Replace 000] with the research plan number (Three digit format, ex: "001" for research plan "RP001")
      • Type of Participant
        • Find/Replace [Replace TYPE OF PARTICIPANT] with the participant type (ex: "Intern" or "Mentor")
      • Research Plan Name
        • Find/Replace [Replace TITLE OF RESEARCH] with the research plan name on the wiki page or the research plan folder (ex: “Intern Intake Interview” or “Mentor Exit Interview”)
    • Copy and paste the edited template from text editor back into this Github Issue, replacing the original text
    • Re-check all the checkboxes above after copying and pasting the edited template
    • Close the text editor
    • Update the issue title
      • Copy
      TWE: IS[Replace YY]: RP[Replace 000]: Research Roadmap: Update/Create
      
      • Choose "Edit" in the title section
      • Paste what you copied into the issue title
      • Choose "Save"
  • Customize the issue settings (located in right sidebar)
    • Under Assignees, assign a Researcher if it has been determined. Otherwise, leave it blank.
    • Under Labels, choose gear Screenshot 2023-01-11 at 10 50 11 AM, and apply the label Research: RP[Replace 000]
    • Under Labels, choose gear Screenshot 2023-01-11 at 10 50 11 AM, and apply the label Participant Type: [Replace TYPE OF PARTICIPANT]
    • Remove the Research 000: missing and Participant Type: missing labels
    • Under Projects, choose gear Screenshot 2023-01-11 at 10 50 11 AM, choose Repository, and choose Program Management
    • Add the milestone: choose gear Screenshot 2023-01-11 at 10 50 11 AM, and choose Research Roadmap Document Creation
    • Remove the label milestone: missing
  • Remove this section
    • After all the checkboxes above are complete and the issue is ready to be worked on, delete all text below the "Instructions for Creating this Issue" (top heading) and above "Overview" (heading below) -- i.e., the issue assignee will never see this part

Dependencies

  • A research setup structure (wiki, GitHub labels, Google Drive, etc.) has been created and approved [REPLACE WITH RESEARCH STRUCTURE ISSUE # IF AVAILABLE]. Use this URL to search the issue tab for potential results
  • [REPLACE WITH RESEARCH ROADMAP ISSUE #] if there is an existing roadmap issue for [Replace TYPE OF PARTICIPANT], Use this URL to search the issue tab for potential results

Overview

We need to update the details of the [Replace TYPE OF PARTICIPANT] Research Roadmap for RP[Replace 000] so that the high level overview captures why we are doing all the research plans with this user group.

During these tasks you will be asked to add link to the Resources/Instructions section, and that section is at the bottom of this issue (go view it now).

Action Items

Customize Resource Links

  • Customize Resource for Wiki Page Links
    • Go to the wiki page: Research Output Overview (Resources # 1.01)
    • Open relevant wiki page for [Replace TYPE OF PARTICIPANT]
    • Copy the link for the [Replace TYPE OF PARTICIPANT] wiki page in your browser
    • In Resources # 2.01, place the link you just copied between parentheses at the end of the line with no space in between the right bracket ] and the left parenthesis (, so it turns into a hyperlink
    • Choose "Update comment" in Github and make sure all the checkboxes above have been checked Screenshot 2023-02-21 at 6 47 15 PM
    • Go to [Replace TYPE OF PARTICIPANT] Research Overview wiki page (Resources # 2.01)
    • Open relevant wiki page for RP[Replace 000]
    • Copy the link for the RP[Replace 000] wiki page in your browser
    • In Resources # 2.02, place the link you just copied between parentheses at the end of the line with no space in between the right bracket ] and the left parenthesis (, so it turns into a hyperlink
    • Choose "Update comment" in Github and make sure all the checkboxes above have been checked Screenshot 2023-02-21 at 6 47 15 PM
  • Customize Resource for Google Drive Folder by Participant Type
    • Choose the "Research by Participant Type" folder on the shared Google Drive (Resources # 1.02)
    • Choose [Replace TYPE OF PARTICIPANT] folder
    • Copy the link of the [Replace TYPE OF PARTICIPANT] folder
      1. Choose the three vertical dots on the right side of the [Replace TYPE OF PARTICIPANT] folder Screenshot 2023-10-10 at 5 58 13 PM
      2. Choose "Share"
      3. Choose "Copy link"
    • In Resources # 2.03, place the link you just copied between parentheses at the end of the line with no space in between the right bracket ] and the left parenthesis (, so it turns into a hyperlink
    • Choose "Update comment" in Github and make sure all the checkboxes above have been checked
  • Customize Resource for [Replace TYPE OF PARTICIPANT]'s Research Roadmap doc
    • Open the [Replace TYPE OF PARTICIPANT] folder (linked in Resources # 2.03)
    • Locate TWE: Research Roadmap: [Replace TYPE OF PARTICIPANT] Google doc in the folder
    • Copy the link of the TWE: Research Roadmap: [Replace TYPE OF PARTICIPANT] Google doc
      1. Choose the three vertical dots on the top right side of the TWE: Research Roadmap: [Replace TYPE OF PARTICIPANT] Google doc Screenshot 2023-10-10 at 5 58 13 PM
      2. Choose "Share"
      3. Choose "Copy link"
    • In Resources # 2.04, place the link you just copied between parentheses at the end of the line with no space in between the right bracket ] and the left parenthesis (, so it turns into a hyperlink
    • Choose "Update comment" in Github and make sure all the checkboxes above have been checked

Check & Fix Research Roadmap Document Formatting

  • Review File Name
    • Open the roadmap document (linked in Resources # 2.04)
    • Confirm that the document uses the following naming convention: TWE: Research Roadmap: [Replace TYPE OF PARTICIPANT]. If it does not follow that format, change the filename to match the project's naming convention.
  • Compare Document Headings
    • With the roadmap document open in one tab (linked in Resources # 2.04), open in another tab the TWE: Template: Research Roadmap (linked in Resources # 1.03)
    • Click inside the roadmap document (linked in Resources # 2.04) and scroll through the document to determine whether the document contains the same headings as the research roadmap template (linked in Resources # 1.03).
  • Adjust Incorrect Document Headings
    • If the document does not have the correct headings, then adjust the headings according to the template.
      • Check that each major heading is formatted as Header 1.
      • To check formatting, place your cursor inside the heading text and look at the Styles dropdown menu next to the Font dropdown menu. If it needs adjusted, select the entire heading text and choose "Header 1" in the Styles dropdown menu.
    • Check off the items below as you review their formatting (a check mark indicates that you've reviewed the item regardless of whether you fixed it or not).
      • Background
      • [Replace TYPE OF PARTICIPANT] Research Goals and Objectives
      • Participants
      • Research Framework and Methodologies
      • Individual Research Plans
        • Research Plan Section Titles (see specific instructions in the next section)
      • Resources
      • Notes
  • Review Research Plan Names and Formatting
    • Confirm that all the research plans section titles are named in RP000: [TITLE OF RESEARCH] format.
    • Confirm each research plan name in the research roadmap document is correct by checking [Replace TYPE OF PARTICIPANT] Research Output Overview page (linked in Resources # 2.01). If they need to be adjusted, fix them according to how they are named in the Research Output Overview page (linked in Resources # 2.01) or ask the UXR lead if there is no corresponding wiki page.
    • Confirm that the research plan names are formatted as Header 2 in the document heading options.
      • To check, place your cursor inside the heading text and look at the Styles dropdown menu next to the Font dropdown menu. If it needs adjusted, select the entire heading text and choose "Header 2" in the Styles dropdown menu.
    • Confirm research plan's subsection has the following sections
      • Goals
      • Requirements
      • Timelines
      • Delivery
      • Follow-up Options
      • Research Analysis
    • Confirm research plan's subsection are formatted as Header 3.
      • To check, place your cursor inside the heading text and look at the Styles dropdown menu next to the Font dropdown menu. If it needs adjusted, select the entire heading text and choose "Header 3" in the Styles dropdown menu.

Update and/or create research roadmap details for [Replace TYPE OF PARTICIPANT] and RP[Replace 000]

  • Update Overview Sections
    • If the [Replace TYPE OF PARTICIPANT] research roadmap overview sections have been drafted, please review and revise the general overview of research roadmap as necessary.
      • Compare the [Replace TYPE OF PARTICIPANT] Research Roadmap against the [Replace TYPE OF PARTICIPANT] Research Overview Wiki Page (linked in Resources # 2.01). If you notice any discrepancy, please inform the team about the discrepancy in the [Replace TYPE OF PARTICIPANT] Research Roadmap by inserting a comment in the Google doc.
      • Read through the following sections to see if they make sense. Check for typos, completeness, and general formatting as you read through each section. If you think the content should be revised, please use "Suggesting Mode" to suggest revisions. Screenshot 2023-07-20 at 5 17 12 PM If you have questions or concerns, please insert comments in the [Replace TYPE OF PARTICIPANT] Research Roadmap Google doc for the UX Research Lead to review.
        • Background about the project/product.
        • Research goals and/or objectives of the type of research.
        • Summary of the target participants.
        • Research framework and methodologies.
    • If the [Replace TYPE OF PARTICIPANT] research roadmap has not been drafted, please fill out the overview sections of the research roadmap by following the steps
      • Open the Research Roadmap for [Replace TYPE OF PARTICIPANT] if it is not open in your browser (Resources # 2.04)
      • Make sure the structure and format of a research roadmap stays consistent. Check Research Roadmap Template (linked in Resources # 1.03) or Report Template - Roadmap Overview below Resources for the structure of the roadmap overview sections if needed.
      • Go to [Replace TYPE OF PARTICIPANT] Research Overview wiki page (Resources # 2.01) to gather information
      • Refer to an existing research roadmap as an example for the research roadmap overview you are creating (Resources # 1.04)
      • Fill out the overview sections of [Replace TYPE OF PARTICIPANT] research roadmap based on the information you gathered
        • Background
        • [Replace TYPE OF PARTICIPANT] Research Goals and Objectives
        • Participants
        • Research Framework and Methodologies
  • Update Research Plan Section
    • If the research roadmap for RP[Replace 000] has been created, please review and revise each subsection under the RP[Replace 000]'s research roadmap as necessary.
      • Compare the RP[Replace 000]'s research roadmap subsections against the RP[Replace 000]'s wiki page (linked in Resources # 2.02). If you notice any discrepancy, please inform the team about the discrepancy in the RP[Replace 000]'s research roadmap by inserting a comment in the Google doc.
      • Read through each section to see if they make sense. Check for typos, completeness, and general formatting as you read through each section. If you think the content should be revised, please use "Suggesting Mode" to suggest revisions. Screenshot 2023-07-20 at 5 17 12 PM If you have questions or concerns, please insert comments in the RP[Replace 000] Research Roadmap Google doc for the UX Research Lead to review.
        • Goals
        • Requirements
        • Timelines
        • Delivery
        • Follow-up Options
        • Research Analysis
    • If the research roadmap for RP[Replace 000] has not been created, please fill out the research roadmap for RP[Replace 000] by following the steps
      • Open the Research Roadmap for [Replace TYPE OF PARTICIPANT] if it is not open in your browser (Resources # 2.04)
      • Identify the placement of RP[Replace 000]'s research roadmap in the ascending sequence in the Google doc
      • Make sure to copy the structure and format of a research plan's research roadmap to keep the documentation consistent. Copy Report Template - Research Plan below Resources to the research roadmap Google Doc if needed.
        • Rename the research plan title RP???: Research Plan Name with RP[Replace 000]: [Replace TITLE OF RESEARCH]
        • Apply formatting to RP[Replace 000]: [Replace TITLE OF RESEARCH]
          • Apply "Header 2" in section title RP[Replace 000]: [Replace TITLE OF RESEARCH]
          • Apply "Header 3" to all the subsections: Goals, Requirements, Timelines, Delivery, Follow-up Options, and Research Analysis
      • Go to RP[Replace 000]'s wiki page (Resources # 2.02) to gather information
      • Refer to an existing research roadmap as an example for the research roadmap overview you are creating (Resources # 1.04)
      • Fill out the research roadmap for RP[Replace 000] based on the information you gathered
        • Goals
        • Requirements
        • Timelines
        • Delivery
        • Follow-up Options
        • Research Analysis
  • Update the Resource Section at the end of research roadmap Google doc
    • Check the final sections (Resources and Notes) to see if they are updated, have functional links, and do not include redundant information.
      • In the Resources section, double check that links to the individual research plans are accurate and complete according to the Overview wiki page (Resources # 2.01).
  • Go to the Table of Contents of [Replace TYPE OF PARTICIPANT] Research Roadmap document once you finish revising or updating the research roadmap draft
  • Update the Table of Contents by clicking on the circle icon Screenshot 2023-07-13 at 4 01 49 PM

Next steps

  • Discuss and review the research roadmap document at the next meeting
  • Make new issues for research plan(s) under the [Replace TYPE OF PARTICIPANT] Research Roadmap if the research plan issue hasn't been created yet
    • Include this issue as the dependency in the newly created research plan issue
  • Product sign-off
    • Research roadmap Google doc (Resources # 2.04)
    • New issues created for research plan(s) under the [Replace TYPE OF PARTICIPANT] Research Roadmap
  • Release the research plan issue when this issue is closed

Resources/ Instructions

Resources for creating this issue

1.01 Wiki: Research Output Overview
1.02 Google Drive Folder: Research by Participant Type
1.03 TWE: Template: Research Roadmap
1.04 TWE: Research Roadmap: Interns

Resources gathered during the completion of this issue

2.01 [Wiki [Replace TYPE OF PARTICIPANT] Research Overview Page]
2.02 [RP[Replace 000] Wiki Page]
2.03 [[Replace TYPE OF PARTICIPANT] Google Drive Folder]
2.04 [TWE: Research Roadmap: [Replace TYPE OF PARTICIPANT]]

Report Template - Roadmap Overview

- [ ] Background
- [ ] [Replace TYPE OF PARTICIPANT] Research Goals and Objectives
- [ ] Participants
- [ ] Research Framework and Methodologies
- [ ] Resources
- [ ] Notes

Report Template - Research Plan (each RP in the roadmap should be in the same structure and format)

- [ ] RP[Replace 000]: [Replace TITLE OF RESEARCH]
   - [ ] Goals
   - [ ] Requirements
   - [ ] Timelines
   - [ ] Delivery
   - [ ] Follow-up Options
   - [ ] Research Analysis 

@pandanista pandanista self-assigned this Jul 18, 2023
@pandanista pandanista changed the title TWE: Create Template Issue: Create or update research roadmap document TWE: Create Template Issue: Create or update research roadmap details Jul 18, 2023
@pandanista
Copy link
Member Author

pandanista commented Jul 18, 2023

This template has been tested by internal TWE team member on issue #448.

@priyatalwar Now this template is ready to be tested by product team.

The reason for creating this template is because the existing issue template Issue: Research: Create Roadmap Details is outdated. Therefore, once passing the testings, this template can either replace the Issue: Research: Create Roadmap Details template in use or saved a new template for roadmap details (vs set up roadmap doc structure).

I incorporated part of #326 into the template above, but they have different approach (#326 is to identify where in the research roadmap needs improvement, and #450 is to update the roadmap doc).

@pandanista pandanista added the Ready for product When the issue is ready for product team to review label Jul 20, 2023
@priyatalwar
Copy link
Member

This template needs to be tested by product so it can be signed off.

@sunannie27
Copy link
Member

Added to PM agenda

@pandanista
Copy link
Member Author

PM has finished the testing using issue #470 and provided feedback in the thread. I've implemented all the changes in the template. This template is ready for project lead to review.

@pandanista pandanista removed the Ready for product When the issue is ready for product team to review label Oct 11, 2023
@pandanista pandanista added Ready for product When the issue is ready for product team to review and removed dependency labels May 2, 2024
@pandanista pandanista self-assigned this May 2, 2024
@pandanista
Copy link
Member Author

pandanista commented May 2, 2024

@sunannie27

@ExperimentsInHonesty
Copy link
Member

Adding to agenda to find out if Ying thinks this template has been sufficiently tested. If not, create a template testing issue out of the new template.

The reason we are asking is that in this comment on the testing issue, Ying indicates its an old template and she has modified it, but at that point in Andrews test, he was 1/2 way through it.

@ExperimentsInHonesty
Copy link
Member

When @sunannie27 finishes the template testing and we publish that template, then @pandanista should use the testing template to make an issue for Sandy to the Creating of Roadmap details template on RP025.

@pandanista
Copy link
Member Author

pandanista commented Jun 4, 2024

@pandanista
Copy link
Member Author

This template is ready for another round of testing. After creating the testing issue, will add the template 2(b) label.

@ExperimentsInHonesty
Copy link
Member

@jinyan0425 Use this testing template to test the issue comment with the Update Research Roadmap template above, which will end up making as your test issue, an issue to Create roadmap details for RP0025. When you have completed the test, the issue will be ready for sandy to be assigned and she will create the roadmap details in this document TWE: Research Roadmap: Other

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
complexity: medium feature: research All issues involving research feature: roadmap feature: template creation (step 1) issue to create a new template (see other labels with test in them) feature: template Participant Type: All role: UX research lead size: 1pt Can be done in 6 hours
Projects
Status: Questions/Review
Development

No branches or pull requests

4 participants