Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

v2 and Non-Contributing Team Members #78

Open
dwilczyn opened this issue Dec 3, 2013 · 0 comments
Open

v2 and Non-Contributing Team Members #78

dwilczyn opened this issue Dec 3, 2013 · 0 comments

Comments

@dwilczyn
Copy link

dwilczyn commented Dec 3, 2013

Several teams have come to me concerned about their v2 team grade because one or more teammates have NON-INTEGRATABLE code.

DO NOT take over and rewrite their code. It is not your responsibility and you won't be penalized for their failure. Here is how I would handle it:

  1. With the project due next Tuesday, I would schedule an integration on Saturday, Sunday at the latest.
  2. With most functioning teams, you will be able to get a running system together. You will be able to tell if a reasonable amount of more work is required to smooth out the edges.
  3. If some components simply don't work, i.e., are not integratable. You must shift into plan B.

Plan B

  1. Remove all traces of the non-integratable code. DO NOT ATTEMPT TO REWRITE IT.
  2. Fix your system to ignore the missing functionality. For example, if the Bank doesn't work, remove it and fix the other agents to ignore banking needs. If the car-code doesn't work, you still have other transportation options. If the PersonAgent is the problem, then you have a problem that you must fix. Obviously, each problem has to analyzed to see if has a straightforward solution.
  3. Push your finalized system onto GIT, documenting what has happened.
  4. For the students whose code was removed or never added, have them checkout "some" running version of the system that they can work with INDEPENDENTLY to try to get their code integrated. This effort will be graded separately from the team's submission.

For students in danger of falling into plan B, you have several days to get your act together; get your code written and unit tested in preparation for integration. I don't mind teammates helping one another, but I hate it when achieving teammates are abused by under-achievers. I'll repeat it again: DO NOT take over and rewrite code that cannot be integrated..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant