Available in PDF here.
RE: Doing Philosophy in Teams.
Invitation to participate in an NEH Digital Humanities Implementation
Dr. Michael Hoffmann
Director of the Philosophy Program
School of Public Policy
December 31, 2014
I would like to invite you to participate in the writing of a grant proposal whose goal is to get funding for a three-year, $325,000 project that focuses on using web-based argument mapping software to support problem-based learning (PBL) in philosophy. PBL is learning in teams. Traditionally, PBL has one goal and two basic strategies. The goal is to stimulate and guide self-directed student learning. The first strategy is to let small groups of students collaborate autonomously, but guided by a “facilitator” or “tutor,” and the second is to confront student teams with a problem that poses a real challenge. As Allyn Walsh (2005) highlights in her tutorial, the goal “is NOT to solve the problem which has been presented. Rather, the problem is used to help students identify their own learning needs as they attempt to understand the problem, to pull together, synthesize and apply information to the problem, and to begin to work effectively to learn from group members as well as tutors.” In PBL students are supposed to acquire on their own the knowledge they need to approach the problem. Students should learn to learn.
Wednesday, December 31, 2014
Monday, December 15, 2014
For the first time in a long time, I have the opportunity to teach a bona fide seminar. The "seminar paper" is a pretty ubiquitous feature of that experience. But to my surprise, I've never thought very explicitly about what an undergraduate seminar paper is supposed to be. So I'm interested in how all of you have explained this to your students: What's its main rhetorical function? What's the proposed length? What are the main components?