Team Descriptions

Alex Garcia

Accomplishes tasks quickly by using extensive knowledge base. Able to use base knowledge of computers in some assignments. Never reads the material prior to meeting. Does fair share of the work, but generally not above and beyond the fair share. Often makes statements implying the team will fail the assignment. Talks about the need to get good grades by turning in quality work. Reminds team of deadlines to help encourage the completion of tasks. Writes checklists that keep the team focused. Asks everyone to contribute ideas so everyone's voice is heard during team meetings. Shares ideas openly with fellow team members.

Jessie Jackson

Checks work to ensure it is generally correct. Communicates high expectations with regard to the quality of assignments. Does fair share of the work, but generally not above and beyond the fair share. Performs a significant amount of work on assignments. Listens to everyone. Seeks input from team members that haven't voiced ideas yet. Able to contribute to all assignments because of an unusually strong understanding of the required mathematical knowledge and skills. Figures out how to do the math for assigned problems. Records team progress and tasks remaining. Sets goals and checkpoints to help the team.

Skyler Lopez

Fails to complete personal taskwork required for the team's assignment. Adds input to the team assignments. Identifies weaknesses in the team's developments. Does not follow up with team members about tasking to ensure understanding. Encourages the team to achieve its highest potential. Talks about the need to get good grades by turning in quality work. Communicates well with the other team members. Asks everyone to contribute ideas so everyone's voice is heard during team meetings. Applies previously gained programming knowledge to complete tasks. Relies on extensive computer skills to complete team assignments.

Thu Jan 23 00:53:24 2025 / IATmSJ4XPUUmdYdndhNIs