Team Descriptions

Chase Anderson

Finishes work as quickly as possible without regard for whether it is done correctly. Talks about the need to get good grades by turning in quality work. Does not try to learn the skills needed to complete the task. Able to use base knowledge of computers in some assignments. Records team progress and tasks remaining. Does not follow up with team members about tasking to ensure understanding. Engages in little taskwork if not pushed by others. Completes the tasks needed. Communicates well with the other team members. Involves everyone in discussions.

Carson Clark

Appropriately assigns roles to team members to get the most productivity out of everyone. Records team progress and tasks remaining. Actively listens to others' opinions and ideas of how things should be done. Seeks input from team members that haven't voiced ideas yet. Often makes statements implying the team will fail the assignment. Usually reads and double-checks the work before submitting it. Engages in little taskwork if not pushed by others. Completes any math required as part of the team's assignments. Demonstrates outstanding mathematics skills. Able to use base knowledge of computers in some assignments.

Kendall Taylor

Turns in acceptable, but not outstanding, work. Generates new ideas to improve the team's assignment that the rest of the team had not thought of. 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. Rarely checks on progress of other team members. Encourages the team members to stay on the tasks. Checks work to ensure it is generally correct. Makes statements indicating a greater concern for just getting done rather than ensuring a quality job. Demonstrates outstanding mathematics skills. Figures out how to do the math for assigned problems.

Thu Dec 5 19:30:52 2024 / QUvtmOGmvVISEUDohR9A6