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.
Carson Clark
Accomplishes tasks quickly by using extensive knowledge base. Able to use base knowledge of computers in some assignments. Identifies weaknesses in the team's developments. Does not give feedback on a problem unless someone else addresses a concern first. Invests time to ensure the team is doing the job well. Finishes work as quickly as possible without regard for whether it is done correctly. Actively listens to others' opinions and ideas of how things should be done. Displays nonverbal signs of frustration, disinterest, or contempt towards working with others on the team. Completes the tasks needed. Sits idly in team meetings.
Pat Hall
Ensures that things get done by asking if each member understands the tasks that they need to accomplish. Distracts the other team members by talking about topics that have nothing to do with the task. Submits work that fails to meet the task requirements explicitly stated by the team. Completes any math required as part of the team's assignments. Finishes work as quickly as possible without regard for whether it is done correctly. Shares ideas openly with fellow team members. Often argues with other teammates. Applies previously gained programming knowledge to complete tasks. Expresses frustration when trying to complete tasks that require task-specific knowledge and skills.
Morgan Hernandez
Does more work than what is needed. Consistently meets the expectations of the assignment. Relies on extensive computer skills to complete team assignments. Applies previously gained programming knowledge to complete tasks. Shares ideas openly with fellow team members. Involves everyone in discussions. Identifies weaknesses in the team's developments. Organizes team meetings. Often makes statements implying the team will fail the assignment. Invests time to ensure the team is doing the job well.
