TEAMWORK A FEW NOTES

MAYBE YOUR ONLY FULL-SCALE TEAM PROJECT AT WWU … 8 weeks A beginning and an end Consistent team membership Negotiation of schedules Areas of expertise Frequent communication … pretty much normal work in business A CHANCE TO GROW OVER THE ENTIRE QUARTER

COMMENTS FROM SUCCESSFUL TEAMS … “Here, everyone helps and supports you.” “I met new people and learned a lot from them. They do not mind sharing their expertise.”

COMMUNICATION CC everyone in your group Don’t be a bottleneck. CC your teammates

“Pair Programming (sometimes referred to as peer programming) is an agile software development technique in which two programmers work as a pair together on one workstation. One, the driver, writes code while the other, the observer, pointer or navigator,[1] reviews each line of code as it is typed in.”Pair Programming “The two programmers switch roles frequently. …” [Wikipedia: _programming

TEAM INTERACTION POLICIES Hotshot Each team will designate their “hotshot” via to Subject line: Team [name]  The hotshot will never sit at the keyboard/mouse when the team is working together, and the hotshot is not allowed to work alone on the team project.*  If the hotshot is spotted at the keyboard by an instructor, …  … the team will receive a 100% deduction on that week’s lab.  … the deliverables will nevertheless still be due and will be evaluated. Therefore, if there are errors, the total deduction will total more than 100% - resulting in negative points on the lab. Team Evaluations At the end of the quarter all team members will evaluate the participation/contribution of their teammates. Students evaluated as “free- riders” and “runaway drivers” by their teammates will receive deductions from their individual points. Team Communication “cc” all teammates whenever contacting the instructors (or other teammates) about the team projects. *The hotshot is allowed to build her/his own separate project in order to build direct, personal experience. This version is not evaluated by the instructor.