Remember that you will be able to view any of these descriptions during the activity simply by rolling your mouse over each student's name.
- Madison Brown
- Identifies weaknesses in the team's developments. Rarely checks on progress of other team members. Respects other team members' opinions. Frequently absent. Applies previously gained programming knowledge to complete tasks. Shows skills in areas where the rest of the team does not have them. Frequently misses team meetings. Consistently meets the expectations of the assignment. Shows little concern about the team's performance on assignments.
- Kendall Lopez
- Communicates well with the other team members. Asks everyone to contribute ideas so everyone's voice is heard during team meetings. Encourages team to check work for errors. Finishes work as quickly as possible without regard for whether it is done correctly. Writes down a checklist of what the team needs to get done for meetings. Helps the team think of issues that have been overlooked. Uses relevant math skills. Shows skills in areas where the rest of the team does not have them. Does fair share of the work, but generally not above and beyond the fair share. Identifies solutions for issues that no one else is able to address.
- Morgan White
- Sets internal deadlines to push the team to complete goals effectively. Identifies weaknesses in the team's developments. Questions things to ensure that processes are the best they can be. Usually reads and double-checks the work before submitting it. Adds input to the team assignments. Routinely late to team meetings. Relies upon an excellent knowledge base that greatly assists in solving the team's problems. Uses relevant math skills. Shares ideas openly with fellow team members. Is often combative when own ideas are not adopted.
Sun Mar 7 18:24:11 2021