Team Descriptions

Madison Brown

Often makes statements implying the team will fail the assignment. Talks about the need to get good grades by turning in quality work. Shows skills in areas where the rest of the team does not have them. Applies previously gained programming knowledge to complete tasks. Does an equal share of the work. Identifies solutions for issues that no one else is able to address. Fails to give status reports to other team members. Listens to everyone's opinions. Writes down a checklist of what the team needs to get done for meetings. Helps the team think of issues that have been overlooked.

Parker Hall

Encourages the team to do better than it normally would. Invests time to ensure the team is doing the job well. Never reads the material prior to meeting. Completes all assigned tasks on time. Shares ideas openly with fellow team members. Often argues with other teammates. Relies on extensive computer skills to complete team assignments. Able to use base knowledge of computers in some assignments. Ensures that things get done by asking if each member understands the tasks that they need to accomplish. Sets internal deadlines to push the team to complete goals effectively.

Alex Robinson

Applies previously gained programming knowledge to complete tasks. Takes the initiative to make sure everyone makes it to the meetings and gets their work done. Records team progress and tasks remaining. Shows up late, if at all, to team meetings. Completes any math required as part of the team's assignments. Is often combative when own ideas are not adopted. Listens to everyone. Checks work to ensure it is generally correct. Often makes statements implying the team will fail the assignment.

Sun Mar 8 18:44:01 2026 / Rh7zsmyKyW9V4N5-6LsLe