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 Hill
Encourages team to check work for errors. Reviews all work before submitting it to the team to ensure it is of top quality. Accomplishes tasks quickly by using extensive knowledge base. Applies previous knowledge of computer programs to tasks. Encourages the team members to stay on the tasks. Gives constructive feedback. Asks everyone to contribute ideas so everyone's voice is heard during team meetings. Communicates well with the other team members. Never reads the material prior to meeting. Turns in acceptable, but not outstanding, work.
Drew Robinson
Finishes work as quickly as possible without regard for whether it is done correctly. Encourages team to check work for errors. Frequently misses team meetings. Completes the tasks needed. Uses computer skills to help solve some problems. Relies upon an excellent knowledge base that greatly assists in solving the team's problems. Shares ideas openly with fellow team members. Ignores other team members' ideas and opinions. Takes the initiative to make sure everyone makes it to the meetings and gets their work done. Identifies weaknesses in the team's developments.
Parker Rodriguez
Encourages the team to achieve its highest potential. Encourages team to check work for errors. Is often combative when own ideas are not adopted. Never reads the material prior to meeting. Completes all assigned tasks on time. Writes down a checklist of what the team needs to get done for meetings. Identifies weaknesses in the team's developments. Relies upon an excellent knowledge base that greatly assists in solving the team's problems. Applies previously gained programming knowledge to complete tasks.
