Team Descriptions

Pat Anderson

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. Checks work to ensure it is generally correct. Does not try to learn the skills needed to complete the task. Uses computer skills to help solve some problems. Turns in acceptable, but not outstanding, work. Does more work than what is needed. Does not give feedback on a problem unless someone else addresses a concern first. Records team progress and tasks remaining.

Harley Jones

Reviews all work before submitting it to the team to ensure it is of top quality. Talks about the need to get good grades by turning in quality work. Identifies weaknesses in the team's developments. Takes the initiative to make sure everyone makes it to the meetings and gets their work done. Able to contribute to all assignments because of an unusually strong understanding of the required mathematical knowledge and skills. Applies previous knowledge of computer programs to tasks. Asks everyone to contribute ideas so everyone's voice is heard during team meetings. Effectively completes tasks, no matter what. Completes any math required as part of the team's assignments.

Parker Lopez

Shares ideas openly with fellow team members. Is often combative when own ideas are not adopted. Relies upon an excellent knowledge base that greatly assists in solving the team's problems. Applies previously gained programming knowledge to complete tasks. Completes any math required as part of the team's assignments. Usually reads and double-checks the work before submitting it. Often makes statements implying the team will fail the assignment. Keeps track of deadlines and holds team members to those deadlines to ensure the project is completed in the time allotted. Reminds team of deadlines to help encourage the completion of tasks.

Sat Apr 26 12:23:12 2025 / GbCdtGV6_5Yby92PnC9AR