Team Descriptions

Remember that you will be able to view any of these descriptions during the activity simply by rolling your mouse over or using tab to focus on each student's name.

Taylor Allen: Usually reads and double-checks the work before submitting it. Makes statements indicating a greater concern for just getting done rather than ensuring a quality job. Listens to everyone. Able to use base knowledge of computers in some assignments. Expresses frustration when trying to complete tasks that require task-specific knowledge and skills. Gives constructive feedback. Ensures that things get done by asking if each member understands the tasks that they need to accomplish. Completes any math required as part of the team's assignments. Generates new ideas to improve the team's assignment that the rest of the team had not thought of.
Reese Clark: Turns in acceptable, but not outstanding, work. Puts in more effort than any other member of the team. Creates goals to help the team monitor its progress. Identifies weaknesses in the team's developments. Relies upon an excellent knowledge base that greatly assists in solving the team's problems. Figures out how to do the math for assigned problems. Redirects negative comments of other team members to keep things positive. Communicates well with the other team members. Encourages the team to do better than it normally would. Checks work to ensure it is generally correct.
London Lewis: Routinely late to team meetings. Completes all assigned tasks on time. Writes down a checklist of what the team needs to get done for meetings. Ensures that things get done by asking if each member understands the tasks that they need to accomplish. Able to use base knowledge of computers in some assignments. Makes statements indicating a greater concern for just getting done rather than ensuring a quality job. Listens to everyone's opinions. Fails to give status reports to other team members.

Tue Mar 21 19:33:29 2023 / hT88ie3VAg-jgldxTqGHZ