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.

Rowan Anderson: Usually reads and double-checks the work before submitting it. Often makes statements implying the team will fail the assignment. Often argues with other teammates. Listens to everyone's opinions. Rarely checks on progress of other team members. Consistently meets the expectations of the assignment. Generates ideas that help the team. Unable to complete basic tasks because he/she is struggling to understand the material.
Chase Clark: Ensures that things get done by asking if each member understands the tasks that they need to accomplish. Takes the initiative to make sure everyone makes it to the meetings and gets their work done. Accomplishes tasks quickly by using extensive knowledge base. Applies previous knowledge of computer programs to tasks. Turns in acceptable, but not outstanding, work. Generates new ideas to improve the team's assignment that the rest of the team had not thought of. Invests time to ensure the team is doing the job well. Makes statements indicating a greater concern for just getting done rather than ensuring a quality job. Listens to everyone. Redirects negative comments of other team members to keep things positive.
Devon Jackson: Redirects negative comments of other team members to keep things positive. Listens to everyone's opinions. Invests time to ensure the team is doing the job well. Encourages the team to do better than it normally would. Uses relevant math skills. Does not try to learn the skills needed to complete the task. Ensures that things get done by asking if each member understands the tasks that they need to accomplish. Shows up late, if at all, to team meetings. Adds input to the team assignments.

Sun Apr 5 13:54:08 2026 / UqmmPYz6RWLXjKrF7NmZY