of the most effective tools for lifelong learning is the ability to reflect and learn from past experience. Reflection helps to clarify our understanding of the world and to create new distinctions and possibilities for the future. It is a way of creating intention. By putting our attention on the perception of what has happened and what we want to achieve, solutions to problems emerge more easily. We also believe reflective skills are among the main characteristics that distinguish excellent engineers from merely good ones. This makes these skills important to teach. This paper describes a set of reflective practices that we implemented in a 9-week course in software engineering at the junior undergraduate level. These techniques, many of them borrowed from professional leadership training programs, include individual, team, and project practices such as retrospectives (e.g., "What went well and what didn't?"), informal chats with guest experts (e.g., "Do they really do it that way in industry?"), workshop simulations (e.g., "How do we decide when to ship a product?"), journaling, and some unusual activities (e.g., "Draw a picture of your team"). To gauge student progress we also used weekly reflective assignments as well as reflective questions on the take-home final exam. All of these techniques were well received by the students, as evidenced by anonymous, detailed end-of-course evaluations, and by voluntary feedback students provided four months after the end of the course. The experience applying reflective practices appears to have influenced a number of the students into viewing their project, careers, social interactions, and life choices in a different, more positive light. Many have continued using several of these techniques after the course. We believe the practices worked particularly well because we set up the course with ample opportunities for students to make mistakes (a fodder for reflection) and learn from them in a non-threatening (academic) environment. While we recommend the approach to engineering educators interested in teaching "soft skills," we caution that to successfully apply it one needs to be comfortable identifying and handling conflict that may emerge.
[1]
Edward J Smaglik,et al.
Experiential Learning From Internships In Construction Engineering
,
2001
.
[2]
D. Finkel,et al.
Teaching with Your Mouth Shut
,
2000
.
[3]
Janet K. Allen,et al.
Learning Essays And The Reflective Learner: Supporting Reflection In Engineering Design Education
,
1997
.
[4]
Lesley Jolly,et al.
Strategies For Developing Reflexive Habits In Students
,
2000
.
[5]
Gerald M. Weinberg,et al.
Learning by Design: Constructing Experiential Learning Programs
,
1990
.
[6]
George Burr Leonard,et al.
Mastery: The Keys to Success and Long-Term Fulfillment
,
1991
.
[7]
Terry Winograd,et al.
Bringing Design to Software
,
1996
.
[8]
Donald A. Sch.
The reflective practitioner: how professionals think in action
,
1983
.
[9]
Durward K. Sobek.
Use Of Journals To Evaluate Student Design Processes
,
2002
.
[10]
Peter J. Denning,et al.
The Profession of IT: The core of the third-wave professional
,
2001,
CACM.
[11]
Steve McConnell,et al.
Rapid Development: Taming Wild Software Schedules
,
1996
.
[12]
Norman L. Kerth,et al.
Project Retrospectives: A Handbook for Team Reviews
,
2001
.
[13]
Barbara M. Olds.
Reflection As An Assessment Measure
,
2000
.
[14]
Valentin Razmov,et al.
When Conflict Helps Learning
,
2003
.
[15]
D. Schoen,et al.
The Reflective Practitioner: How Professionals Think in Action
,
1985
.
[16]
D. Keirsey.
Please Understand Me II: Temperament, Character, Intelligence
,
1998
.
[17]
Mark R. Eaker,et al.
Pegasus Communications
,
2006,
SSRN Electronic Journal.