Editing DUB Seminar (Summer 2022)
From CommunityData
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
<div style="float:right;" class="toclimit-3">__TOC__</div> | <div style="float:right;" class="toclimit-3">__TOC__</div> | ||
=DRAFT! Not yet finished= | |||
:'''Design, Use, Build Seminar''' ('''HCID 590 A''') | :'''Design, Use, Build Seminar''' ('''HCID 590 A''') | ||
:'''Instructor:''' [https://kayleachampion.com Kaylea Champion] / [mailto:kaylea@uw.edu kaylea@uw.edu] | :'''Instructor:''' [https://kayleachampion.com Kaylea Champion] / [mailto:kaylea@uw.edu kaylea@uw.edu] | ||
:'''Office Hours:''' By appointment (I'm usually available via chat during "business hours.") Use | :'''Office Hours:''' By appointment (I'm usually available via chat during "business hours.") Use [https://harmonizely.com/kaylea to schedule time with me]. If you schedule a meeting, we'll meet in the Jitsi room (<code>kayleaoffice</code>) -- you'll get a link to it through the scheduling app. | ||
:'''Meeting Times:''' Wednesday 12-1pm and several other 90-minute sessions (see [[#Class Schedule|the class schedule below]]) | :'''Meeting Times:''' Wednesday 12-1pm and several other 90-minute sessions (see [[#Class Schedule|the class schedule below]]) | ||
:'''Important Links''': | :'''Important Links''': | ||
Line 71: | Line 73: | ||
For the purposes of tracking participation, I am logging our Slack channel and will generate statistics each week of who has participated and when/how much they posted. I don't have a target word count that I'm looking for and I definitely understand that sometimes a thoughtful short message may reflect a bunch of research. That said, I do expect that (a) everybody will post every week, and (b) the posts will be substantial enough to suggest something in the range of 15-20 minutes of thoughtful effort. | For the purposes of tracking participation, I am logging our Slack channel and will generate statistics each week of who has participated and when/how much they posted. I don't have a target word count that I'm looking for and I definitely understand that sometimes a thoughtful short message may reflect a bunch of research. That said, I do expect that (a) everybody will post every week, and (b) the posts will be substantial enough to suggest something in the range of 15-20 minutes of thoughtful effort. | ||
=== Group Synthesis Responses [Due Monday after | === Three Capstone Group Synthesis Responses [Due the Monday after the facilitated discussions @ 6pm ] === | ||
There are six research talks this quarter, and three face-to-face discussion sections. After each "set" -- two talks and a face to face discussion section -- your task is to set aside 45-60 minutes to discuss each pair of talks | There are six research talks this quarter, and three face-to-face discussion sections. After each "set" -- two talks and a face to face discussion section -- your task is to set aside 45-60 minutes to discuss each pair of talks with your capstone project groups. I'm hoping this makes things easier logistics-wise because you'll be meeting with these folks regularly as part of your projects. Your objective is to develop a synthesis | ||
==== Synthesis Response Examples ==== | ==== Synthesis Response Examples ==== | ||
Line 79: | Line 81: | ||
Your response might be inspired by one of these formats or you might follow your own path: | Your response might be inspired by one of these formats or you might follow your own path: | ||
* Analysis: Why or how is the research being presented considered to be important? What conversation does it contribute to? What's puzzling or confusing about what was described? | * Analysis: Why or how is the research being presented considered to be important? What conversation does it contribute to? What's puzzling or confusing about what was described? [Analysis Response Example] | ||
* Same Approach, New Context: Given the same approach, methods, or point of view that you saw described in the talk, what would it look like to explore a different context or problem space using this approach? | * Same Approach, New Context: Given the same approach, methods, or point of view that you saw described in the talk, what would it look like to explore a different context or problem space using this approach? | ||
* New Approach, Same Context: Given the same overall problem space, organization, cultural phenomenon, etc. that you saw described in the talk, what would it look like to explore it using a different approach or method? | * New Approach, Same Context: Given the same overall problem space, organization, cultural phenomenon, etc. that you saw described in the talk, what would it look like to explore it using a different approach or method? | ||
Line 88: | Line 90: | ||
* Retrospective: Thinking back over these talks and all the many other talks you've attended as part of the DUB seminar (see [https://dub.washington.edu/seminar.html#tab_previous_seminars past talks list]), what themes do you identify? Are there tensions or conflicts that emerge within these themes? | * Retrospective: Thinking back over these talks and all the many other talks you've attended as part of the DUB seminar (see [https://dub.washington.edu/seminar.html#tab_previous_seminars past talks list]), what themes do you identify? Are there tensions or conflicts that emerge within these themes? | ||
Your deliverable is to post the following to pinned Slack discussion threads that I'll create for the purpose: | |||
# A short summary of your conversation, using one of the above ways of responding or your own approach (shoot for 200 words). | |||
My understand is that all the project groups have three people. As a result, I'll expect each of you to take the lead in posting your group's contributions to the pinned thread during the quarter. Also, please remember to mention your teammates when you post so that I know whose conversation you are reporting back about! | My understand is that all the project groups have three people. As a result, I'll expect each of you to take the lead in posting your group's contributions to the pinned thread during the quarter. Also, please remember to mention your teammates when you post so that I know whose conversation you are reporting back about! | ||
Line 98: | Line 100: | ||
== Grading and Assessment == | == Grading and Assessment == | ||
This course is offered credit/no credit. Although you will not receive a numeric grade, passing this class is not automatic and I will assess your work and evidence of learning throughout the quarter. You can find details about my approach to assessment and my very detailed grading rubric on [[User: | This course is offered credit/no credit. Although you will not receive a numeric grade, passing this class is not automatic and I will assess your work and evidence of learning throughout the quarter. You can find details about my approach to assessment and my very detailed grading rubric on [[User:Benjamin Mako Hill/Assessment|my assessment page]]. Although I don't expect this to be a problem, you'll need to have credit for at least 2/3 of the assignments in the class in order to get credit for the class: | ||
I will assign points for each of following items according to the weights below: | I will assign points for each of following items according to the weights below: | ||
* Weekly slack conversation: 40% | * Weekly slack conversation: 40% | ||
* | * Bi-weekly group discussions: 30% | ||
* | * Facilitated group discussion: 30% | ||
== Administrative Notes and Resources == | == Administrative Notes and Resources == |