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.
- Alex Harris
- Listens to everyone. Is often combative when own ideas are not adopted. Completes all assigned tasks on time. Comes up with important ideas during team brainstorming. Records team progress and tasks remaining. Distracts the other team members by talking about topics that have nothing to do with the task. Shows skills in areas where the rest of the team does not have them. Able to use base knowledge of computers in some assignments. Usually reads and double-checks the work before submitting it. Questions things to ensure that processes are the best they can be.
- Jessie Johnson
- Seeks input from team members that haven't voiced ideas yet. Shares ideas openly with fellow team members. Often coordinates meetings when others forget. Reminds team of deadlines to help encourage the completion of tasks. Questions things to ensure that processes are the best they can be. Applies previously gained programming knowledge to complete tasks. Relies upon an excellent knowledge base that greatly assists in solving the team's problems. Does fair share of the work, but generally not above and beyond the fair share. Routinely late to team meetings.
- Jamie Wilson
- Often makes statements implying the team will fail the assignment. Communicates well with the other team members. Redirects negative comments of other team members to keep things positive. Encourages the team members to stay on the tasks. Sets internal deadlines to push the team to complete goals effectively. Applies previously gained programming knowledge to complete tasks. Accomplishes tasks quickly by using extensive knowledge base. Submits work that fails to meet the task requirements explicitly stated by the team.