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

Interview Priority Analysis: 37 #108

Open
10 of 12 tasks
Tracked by #199
raquelnish opened this issue Dec 20, 2020 · 6 comments
Open
10 of 12 tasks
Tracked by #199

Interview Priority Analysis: 37 #108

raquelnish opened this issue Dec 20, 2020 · 6 comments
Assignees
Labels
feature: missing Interview length: large Interviews between 61 and 80 minutes PA: Coding PBV: UXR Team Management Issues from the UXR Team Management board from before the migration (see wiki) role: missing size: missing

Comments

@raquelnish
Copy link
Contributor

raquelnish commented Dec 20, 2020

Interview length

78 min.

Overview

For UXR team, we need to process & analyze Interview number 37 in order to complete our analysis phase.

Instructions for working this issue

Do the action items defined by the checkboxes. Each numbered step is a discrete task. We encourage you to complete all the tasks for this brigade's interview, however, you can stop after any of the numbered tasks.

Action Items

  • Assign yourself to this issue (see animated GIF below)
  • Move this issue from the ‘Prioritized Backlog’ to ‘In progress’ (see animated GIF below)

This brigade interview needs the following work done:

  • 1. Transcription verification
    • Add PA Data organization label & remove PA Transcription verification label
  • 2. Data organization
    • Add PA coding label & remove PA Data organization label.
  • 3. Coding
    • Add PA Tagging label & remove PA Coding label.
  • 4. Tagging
    • Mark this issue as Done by clicking the button on the bottom of the issue
      Screen Shot 2021-01-26 at 10 41 35 AM

Reporting progress

  • Be sure to check the box when you finish an action item.
  • Report your progress weekly in a comment below using the following format:
    • Progress:

    • Blockers:

    • Availability
:
    • Estimated date of completion:

Stopping mid issue


Reasons:

  • Got personally busy, can’t finish
  • 
Only want to do a specific type of task per interview
  • There is a blocker in the way of finishing and I still have time to work on other issues


What to do if you have to stop working mid issue:

  • Note your progress in the checkboxes
  • Add a note in the comments with details
  • Move the issue to the questions/review column


Unassigning yourself from this issue

If you are finished with one of the 4 Action Items and you are not going to do the next one

  • Move this issue from the ‘In progress’ to the ‘Prioritized Backlog’(see animated GIF below)
  • Unassign yourself from this issue (see animated GIF below)

Resources/Instructions

Interview Data Sheet
Transcription Verification Instructions
Data Organization Instructions
Coding Instructions
Tagging Instructions

Assign & Unassign yourself to this issue

Assign & Unassign

Move this issue from the ‘Prioritized Backlog’ to the ‘In progress’ & back

Prioritized to In progress & back

@Baleja
Copy link
Contributor

Baleja commented Jan 18, 2021

Progress:
Blockers: Hey there I am stuck on: Instructions for Data organization question 11 & 12
Availability: Approx 6 hrs
ETA: soon!

@Baleja
Copy link
Contributor

Baleja commented Jan 19, 2021

Make sure column F is filled with pasted quotes to continue to the next stage.

@Baleja
Copy link
Contributor

Baleja commented Jan 25, 2021

Still having a little difficulty getting from data organisation to coding.

Please check Brigade highest priorities With Code for Tuscon at the bottom, There are notes in the ranking column instead.

@Baleja Baleja added PA: Coding Interview length: large Interviews between 61 and 80 minutes and removed PA: Data Organization labels Jan 25, 2021
@MarianneAnthonette
Copy link
Contributor

@MarianneAnthonette aka me: I'll audit the transcription sheet (and make notes for Serena for next time) and fix the data organization part as well on Friday.

Don't start coding until I send a message back to you.

@MarianneAnthonette
Copy link
Contributor

MarianneAnthonette commented Jan 30, 2021

@Baleja Yeah, I don't have time to finish fixing the transcription sheet. Go back to the sheet and make the following edits:

  • I went through the Actual cleaned input column and moved text around (you missed the Code of Conduct question). You need to transcribe the entire interview, so you also have to transcribe row 114 and onward. The response in row 123 seems crucial and needs to be moved into the additional topics response row.
  • I went through and deleted the timestamps and some capitalization fixes, but you have to do this for all the remaining errors.
  • I did fix the transcription and separating out ideas for a few questions (you can tell if the data is in col F or onward). This means that they don't need to be worked on. Use this a reference.
  • When you separate out ideas, make sure you don't remove text that provides context. The goal is just to break the text apart. Leave it in there. A lot of your previous data organization deleted a lot of crucial text (it's duplicated in the Old Transcription tab).

Focus on fixing the transcription sheet and separating the ideas, and message me back. I've deleted Dan's responses on the consolidated data sheets.

@bdavis73
Copy link

Transcript verification is complete. Updated status and label.

@ExperimentsInHonesty ExperimentsInHonesty added the PBV: UXR Team Management Issues from the UXR Team Management board from before the migration (see wiki) label Aug 21, 2024
@github-project-automation github-project-automation bot moved this to Prioritized Backlog in BOP: Project Board Aug 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature: missing Interview length: large Interviews between 61 and 80 minutes PA: Coding PBV: UXR Team Management Issues from the UXR Team Management board from before the migration (see wiki) role: missing size: missing
Projects
Status: Prioritized Backlog
Development

No branches or pull requests

6 participants