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.
Quinn Anderson
Never reads the material prior to meeting. Completes all assigned tasks on time. Actively listens to others' opinions and ideas of how things should be done. Frequently absent. Often coordinates meetings when others forget. Reminds team of deadlines to help encourage the completion of tasks. Shows skills in areas where the rest of the team does not have them. Able to use base knowledge of computers in some assignments. Often makes statements implying the team will fail the assignment.
Chase Hall
Organizes team meetings. Encourages the team members to stay on the tasks. Shares ideas openly with fellow team members. Redirects negative comments of other team members to keep things positive. Turns in acceptable, but not outstanding, work. Adds little, if anything, to team assignments. Encourages the team to achieve its highest potential. Encourages team to check work for errors. Relies on extensive computer skills to complete team assignments.
Alex Johnson
Applies previously gained programming knowledge to complete tasks. Engages in little taskwork if not pushed by others. Turns in acceptable, but not outstanding, work. Records team progress and tasks remaining. Does not give feedback on a problem unless someone else addresses a concern first. Often makes statements implying the team will fail the assignment. Usually reads and double-checks the work before submitting it. Asks everyone to contribute ideas so everyone's voice is heard during team meetings. Actively listens to others' opinions and ideas of how things should be done.
