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.
Alex Garcia
Talks about the need to get good grades by turning in quality work. Helps the team think of issues that have been overlooked. Creates goals to help the team monitor its progress. Does more work than what is needed. Listens to everyone. Cheers on teammates. Applies previously gained programming knowledge to complete tasks. Shows skills in areas where the rest of the team does not have them.
Quinn Harris
Listens to everyone. Is often combative when own ideas are not adopted. Turns in acceptable, but not outstanding, work. Always offers ideas about how to complete tasks, no matter what the task is. Able to use base knowledge of computers in some assignments. Expresses frustration when trying to complete tasks that require task-specific knowledge and skills. Ensures that things get done by asking if each member understands the tasks that they need to accomplish. Does not mention problems right away, but later comments about having noticed those issues. Ignores errors in the work and suggests that it is ok to submit as is without fixing errors.
Sage Hernandez
Actively listens to others' opinions and ideas of how things should be done. Boosts team morale by complimenting members on their work. Shows skills in areas where the rest of the team does not have them. Applies previous knowledge of computer programs to tasks. Records team progress and tasks remaining. 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. Generates ideas that help the team. Completes all assigned tasks on time.
