Formal policy and process for dealing with non-performing team members
Formal policy and process for dealing with dysfunctional teamsIndividual projects vary widely, of course, with computing needs varying accordingly. In CS, we are lucky that the main "supplies" we need for our projects are generally free: the laptops/desktops that we already use every day, and open source packages, IDEs, and other tools. There are some projects, however, that may need special resources; here are a couple of useful links.
Instructions on creating easy-to-use task report for your mentor, including a pre-fab template
The CS Capstone Sequence is a collaborative effort between CS faculty and graduate students aimed at efficiently delivering a superior Capstone experience, while engaging a maximum number of faculty and their expert perspectives in the process.
The Course Organizer is the lead faculty member responsible for the course, trains and supervises the Team Mentors, resolves problems and conflicts, and serves as the final authority for all class-related matters. The Organizer shapes the entire experience by working with industry and other outside contacts to solicit, evaluation, refine, and present the projects proposed for each year's sequence. The Organizer also sets the calendar schedule for the course and its deliverables, and generally makes sure that things are rolling smoothly. In the initial semester (CS476, Requirements Acquisition), the Organizer presents the lecture portion of the course, which includes not just lectures but much in-class discussion of best practices, deliverables quality and planning, small presentations, and other in-class exercises...while also training and working with the Team Mentors, who develop a close working relationship with each team and have primary responsibility for evaluating individual team performance. In the second semester (CS486, Capstone Design), the Organizer continues as overall organizer and final authority for all course matters, but the Team Mentors move into more central focus as the maximum effort shifts towards getting each team's planned software product implemented, tested and refined, and delivered to the project client.
Isaac Shaffer
|
 |
Dr. Eck Doerry |
 |
Graduate Team Mentors are a vital part of the CS Capstone concept, bringing a wide variety of expertise to bear for their assigned Capstone teams. As teams are formed and team mentors are assigned, mentors are able to select projects that they are particularly interested in or have relevant experience for. As the two-semester sequence progresses, Team Mentors play an increasingly intensive role in mentoring the team, monitoring project progress, and helping evaluating the extent to which each team member is contributing to team products and meeting the specific learning goals set for Capstone.