Team Descriptions

Chase Clark

Makes statements indicating a greater concern for just getting done rather than ensuring a quality job. Does an equal share of the work. Frequently misses team meetings. Writes down a checklist of what the team needs to get done for meetings. Records team progress and tasks remaining. Learned computer skills required for the assignment so the team could complete the task. Applies previous knowledge of computer programs to tasks. Shares ideas openly with fellow team members. Disregards abstract and creative ideas from other team members.

Devon Davis

Talks about the need to get good grades by turning in quality work. Finishes work as quickly as possible without regard for whether it is done correctly. Able to contribute to all assignments because of an unusually strong understanding of the required mathematical knowledge and skills. Applies previously gained programming knowledge to complete tasks. Listens to everyone. Fails to give status reports to other team members. Ensures that things get done by asking if each member understands the tasks that they need to accomplish. Provides irrelevant information that further confuses the team when the team is attempting to overcome a problem. Completes all assigned tasks on time. Adds little, if anything, to team assignments.

Skyler Miller

Shows skills in areas where the rest of the team does not have them. Uses relevant math skills. Performs a significant amount of work on assignments. Completes any math required as part of the team's assignments. Reminds team of deadlines to help encourage the completion of tasks. Provides irrelevant information that further confuses the team when the team is attempting to overcome a problem. Usually reads and double-checks the work before submitting it. Questions things to ensure that processes are the best they can be. Cheers on teammates. Respects other team members' opinions.

Fri Dec 12 22:17:09 2025 / YgxxLFjNaEc8aIhD312CR