Not logged in
Talk
Contributions
Create account
Log in
Navigation
Main page
About
People
Publications
Teaching
Resources
Research Blog
Wiki Functions
Recent changes
Help
Licensing
User page
Discussion
Edit
View history
Editing
User:Groceryheist/online communities fall 2024 draft syllabus
(section)
From CommunityData
Jump to:
navigation
,
search
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
=== Case analysis discussions === In the other have of class sessions where we do not have a quiz, we will have a discussion to analyze a case. Analyzing these cases develops our skills in applying the course material to practical real-world decisions that actors in real-world situations face. This style of case-based assessement is common in business schools, but less common in other fields. In a case analysis discussion, students prepare by studying readings on an examle—perhaps up to 35 pages—about a community or organization and a challenging decision it faces. Pay close attention to readings marked as “[Case]” in the syllabus in order to prepare for the case. '''I will not cover case material in class or lecture.''' We will dive right into the case discussion at the beginning of class and I expect you to be prepared to participate in a critical discusion. <span id="cold-calling"></span> ==== Cold calling ==== During the case analysis portion of class, I will lead a structured discussion in which we will systematically break down the problem situation and construct recommendations for the actors using the [http://en.wikipedia.org/wiki/Socratic_method socratic method]. Some students are always more open and confident in speaking during open-ended class discussions than others. Therefore, in the interest of fairness, I will use a randomized system for choosing which student to call on when I ask these questions. This system is designed to ensure that every student is called on about the same number of times over the semester, and to avoid calling on the same student too frequently. <span id="case-analysis-assement"></span> ==== Case analysis assement ==== When a student is called upon, I will note the quality of their answer in terms of ''engagement'', ''preparedness'', and ''fluency'' each on a 4 point scale, for a total of 12 points each time a student is called upon. An ''engaged'' answer shows that the student has been attentive to the current discussion. ''Preparedness'' demonstrates that a student has done the reading to prepare for the case discussion. ''Fluency'' reflects command over the concepts and language from the course material overall. Each student will be called on approximately, but not exactly the same number of times. Therefore, to make grading fair, I will follow the following procedure to award 120 points for case discussions: I will drop the bottom 10% of the questions, average the remaining scores, and then multiply by 100. I will be quite generous in these assessments. Students who keep up with the course material, prepare for the cases, and are present in class when they are called on should have little difficulty earning near-perfect scores for the case analyses. <span id="schedule"></span>
Summary:
Please note that all contributions to CommunityData are considered to be released under the Attribution-Share Alike 3.0 Unported (see
CommunityData:Copyrights
for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource.
Do not submit copyrighted work without permission!
To protect the wiki against automated edit spam, we kindly ask you to solve the following CAPTCHA:
Cancel
Editing help
(opens in new window)
Tools
What links here
Related changes
User contributions
Logs
View user groups
Special pages
Page information