Working in teams
Why work in teams?
- We previously had more limited lab resources in the past such that
people could not be assigned machines individually.
- More importantly, I want to encourage communication and
coordination on sysadmin tasks, and have people experience what it
means to work together with other sysadmins.
Team work in this class
- Teams should be two or three people.
- As much as possible, team choice is up to you.
- Please form teams by Thursday so we can finish our virtual lab
setup in time for the first assignment. People not in a team as of
Thursday will be assigned to teams by me.
Grading and teams
- Please try to distribute work evenly among team members.
- Notify other team members and me of planned absences in
advance.
- Since we will be using git extensively for class work, I will
monitor git commits for a team to see whether all team members are
making contributions.
- In general, if team members are contributing in an equitable
way, all members get equal credit for an assignment. There is a
minimum requirement that you must make at least one non-trivial
commit for an assignment (to either Puppet code or related
assignment materials) to receive credit for that assignment. A
"non-trivial commit" does something toward the requirements of that
assignment (adding code, fixing a bug, or adding material that
answers an assignment question).
- If a team appears to be having a problem with people not
sharing work equitably, I will meet with the team to discuss the
problem and to decide whether to assign unequal credit for an
assignment.
Next ->
Steve VanDevender