Team Descriptions

Skyler Allen

Ensures that things get done by asking if each member understands the tasks that they need to accomplish. Sets goals and checkpoints to help the team. 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. Applies previously gained programming knowledge to complete tasks. Expresses frustration when trying to complete tasks that require task-specific knowledge and skills. Routinely late to team meetings. Completes the tasks needed. Shares ideas openly with fellow team members.

Rowan Clark

Does fair share of the work, but generally not above and beyond the fair share. Sits idly in team meetings. Often coordinates meetings when others forget. Helps the team think of issues that have been overlooked. Demonstrates outstanding mathematics skills. Applies previous knowledge of computer programs to tasks. Communicates high expectations with regard to the quality of assignments. Talks about the need to get good grades by turning in quality work. Shares ideas openly with fellow team members. Cheers on teammates.

Sidney White

Identifies weaknesses in the team's developments. Listens to everyone's opinions. Is often combative when own ideas are not adopted. Invests time to ensure the team is doing the job well. Finishes work as quickly as possible without regard for whether it is done correctly. Never reads the material prior to meeting. Does an equal share of the work. Able to use base knowledge of computers in some assignments.