Team Descriptions

Alex Hall

Often makes statements implying the team will fail the assignment. Encourages team to check work for errors. Adds little, if anything, to team assignments. Does an equal share of the work. Records team progress and tasks remaining. Does not follow up with team members about tasking to ensure understanding. Uses computer skills to help solve some problems. Expresses frustration when trying to complete tasks that require task-specific knowledge and skills. Actively listens to others' opinions and ideas of how things should be done.

Parker Hill

Encourages the team to do better than it normally would. Usually reads and double-checks the work before submitting it. Organizes team meetings. Records team progress and tasks remaining. Comes up with important ideas during team brainstorming. Consistently meets the expectations of the assignment. Figures out how to do the math for assigned problems. Shows skills in areas where the rest of the team does not have them. 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.

Morgan Jackson

Turns in acceptable, but not outstanding, work. Identifies solutions for issues that no one else is able to address. Often makes statements implying the team will fail the assignment. Usually reads and double-checks the work before submitting it. Listens to everyone. Is often combative when own ideas are not adopted. Uses relevant math skills. Accomplishes tasks quickly by using extensive knowledge base. Creates goals to help the team monitor its progress. Helps the team think of issues that have been overlooked.