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.

Carson Allen: Consistently meets the expectations of the assignment. Does more work than what is needed. Listens to everyone. Displays a negative attitude towards anything that the team does. Talks about the need to get good grades by turning in quality work. Questions things to ensure that processes are the best they can be. Appropriately assigns roles to team members to get the most productivity out of everyone. Identifies weaknesses in the team's developments. Figures out how to do the math for assigned problems. Shows skills in areas where the rest of the team does not have them.
Addison Hill: Communicates well with the other team members. Involves everyone in discussions. Provides valuable input for accomplishing team assignments. Completes the tasks needed. Relies on extensive computer skills to complete team assignments. Applies previously gained programming knowledge to complete tasks. Writes checklists that keep the team focused. Records team progress and tasks remaining. 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.
Chase King: Listens to everyone's opinions. Boosts team morale by complimenting members on their work. Generates new ideas to improve the team's assignment that the rest of the team had not thought of. Turns in acceptable, but not outstanding, work. 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. Applies previous knowledge of computer programs to tasks. Does not try to learn the skills needed to complete the task. Writes down a checklist of what the team needs to get done for meetings. Identifies weaknesses in the team's developments.

Sat Jul 27 01:50:29 2024 / 1Nl_pGyW12kC3FBy6ex4n