Team Descriptions

Pat Hall

Boosts team morale by complimenting members on their work. Listens to everyone. Helps the team think of issues that have been overlooked. Provides irrelevant information that further confuses the team when the team is attempting to overcome a problem. Applies previously gained programming knowledge to complete tasks. Relies upon an excellent knowledge base that greatly assists in solving the team's problems. Invests time to ensure the team is doing the job well. Encourages the team to do better than it normally would. Submits work that fails to meet the task requirements explicitly stated by the team. Adds input to the team assignments.

Robin Johnson

Accomplishes tasks quickly by using extensive knowledge base. Able to use base knowledge of computers in some assignments. Is often combative when own ideas are not adopted. Actively listens to others' opinions and ideas of how things should be done. Encourages the team members to stay on the tasks. Provides irrelevant information that further confuses the team when the team is attempting to overcome a problem. Comes up with important ideas during team brainstorming. Does an equal share of the work. Talks about the need to get good grades by turning in quality work. Often makes statements implying the team will fail the assignment.

Skyler Thomas

Does fair share of the work, but generally not above and beyond the fair share. Puts in more effort than any other member of the team. Appropriately assigns roles to team members to get the most productivity out of everyone. Helps the team think of issues that have been overlooked. Uses computer skills to help solve some problems. Demonstrates outstanding mathematics skills. Usually reads and double-checks the work before submitting it. Communicates high expectations with regard to the quality of assignments. Redirects negative comments of other team members to keep things positive. Listens to everyone's opinions.

Fri Dec 12 22:32:28 2025 / hVyRi3xrLzl48L6j73gKd