June 20, 2010
June 20, 2010
June 23, 2010
15.3.1 - 15.3.8
“Survivor” Meets Senior Project Abstract
We have all seen the formation of tribes and cliques on the latest edition of the television hit Survivor. Has Survivor mentality invaded your senior projects as well? For the last ten years or so, engineering programs nationwide have, with varying degrees of success, tried to incorporate the ABET-required outcome of “ability to function on multidisciplinary teams.”1 While recognizing that all engineers must function on such teams in the real world, implementing them in the academic context poses substantial challenges. Nonetheless, I would argue that it is either extremely difficult or impossible to evaluate how well we have accomplished this outcome without putting students into the situation where they must actually work with members of other disciplines to accomplish a significant design. Even after such teams have been formed, the vagaries of academia, and the real world, interfere with our ability to measure student function, or dysfunction, within these teams. This paper presents a short history of efforts at the United States Air Force Academy, focusing on the projects sponsored by the Department of Electrical and Computer Engineering and the assessment techniques used to evaluate our students‟ ability to function on multidisciplinary teams.
One method that we and others have used to assess the performance of students on teams is a peer rating scheme. There are a variety of approaches.2-10 One component is usually a weighting system used to enforce reasonable grades and prevent the inevitable effect of team members all wanting to get good “grades” in the component of team performance. This is usually accomplished by limiting the average grade given to some value or renorming the student submissions to establish the desired average and variance. 2, 3 This can be effective, but if the variance is changed significantly, it may hide problems in team members working effectively together. A particularly difficult problem to deal with is the formation of sub-groups within the project team. In our experience this most commonly occurs with engineers from various disciplines forming a clique or tribe and rating the members of their tribe highly while penalizing those from other disciplines. When this occurs, the team cohesiveness and focus on the goal of completing the design successfully can be compromised, as team members try to insure that the majors in their own discipline get better grades than those in other disciplines. We have named this phenomenon the “Survivor” effect. We will discuss our approach to defeating this divisive aspect of assessing the performance of students on multidisciplinary teams.
In the early 1990s, many engineering programs accomplished the ABET requirement for design experience using a senior design project involving a single student. Students were typically enrolled in a single “Design Project” course and completion of the design and course constituted success in the required element. As ABET attention to industrial concerns increased, the importance of working as teams of engineers became apparent. Early on, these teams were limited to engineers, or more correctly students, from a single discipline or engineering major. Although students had to work together to accomplish the design goal, the scope of the design projects led to very highly integrated teams with a narrow focus and left little room for formation of sub-teams competing for team resources.
Dudevoir, G., & Laffely, A., & Mundy, A. J. (2010, June), "Survivor" Meets Senior Project Paper presented at 2010 Annual Conference & Exposition, Louisville, Kentucky. 10.18260/1-2--16267
ASEE holds the copyright on this document. It may be read by the public free of charge. Authors may archive their work on personal websites or in institutional repositories with the following citation: © 2010 American Society for Engineering Education. Other scholars may excerpt or quote from these materials with the same citation. When excerpting or quoting from Conference Proceedings, authors should, in addition to noting the ASEE copyright, list all the original authors and their institutions and name the host city of the conference. - Last updated April 1, 2015