Team Descriptions

Remember that you will be able to view any of these descriptions during the activity simply by rolling your mouse over or using tab to focus on each student's name.

Hayden Lee: Does fair share of the work, but generally not above and beyond the fair share. Sits idly in team meetings. Identifies weaknesses in the team's developments. Does not mention problems right away, but later comments about having noticed those issues. Talks about the need to get good grades by turning in quality work. Often makes statements implying the team will fail the assignment. Often encourages teammates' thoughts and opinions. Listens to everyone's opinions. Uses computer skills to help solve some problems. Expresses frustration when trying to complete tasks that require task-specific knowledge and skills.
Casey Miller: Learned computer skills required for the assignment so the team could complete the task. Applies previously gained programming knowledge to complete tasks. Checks work to ensure it is generally correct. Makes statements indicating a greater concern for just getting done rather than ensuring a quality job. Does fair share of the work, but generally not above and beyond the fair share. Effectively completes tasks, no matter what. Encourages the team members to stay on the tasks. Writes down a checklist of what the team needs to get done for meetings. Boosts team morale by complimenting members on their work. Listens to everyone.
Quinn Thompson: Respects other team members' opinions. Boosts team morale by complimenting members on their work. Learned computer skills required for the assignment so the team could complete the task. Records team progress and tasks remaining. Sets goals and checkpoints to help the team. Does an equal share of the work. Sits idly in team meetings. Encourages the team to do better than it normally would. Invests time to ensure the team is doing the job well.

Tue Jan 27 06:10:02 2026 / eWymvAMVt3BnegCVWhdV2