I compute a single grade for the project, based on the following percentages:
I then apply an individual contribution multiplier for each person. This value is based on my observations as well as the evaluations by your client, any consultants, and your peers. The multiplier ranges from .7 to 1.1, but a value above 1 is only used in exceptional cases. Basically, I do not believe that you should be able to get a better grade than the product you produced.
A few more details:
Process includes whether you are interacting appropriately as a team, with me, and with your client. Are you addressing issues as they arise? It includes professionalism in your dealings with your client and your professor and whether you are usually on time with deliverables or habitually late. It includes your web site and the materials that you produce as steps to produce the other artifacts. I will be grading your processs on a weekly basis and posting it on Sakai. I will be grading both the team and the individuals. The following gives you a flavor of what you should be focusing on throughout the semester.
Requirements Phase: In the first 5 weeks, you should have all of the pieces together to be able to proceed with the project. You should have a web site up and running and an initial schedule. All key platform decisions should be made, all team members should have working development environments, and specific responsibilities should be assigned to team members. Finally, you and the client should have an agreenment on the requirements.
Development Phase: In the middle 5 weeks, you should be in an ongoing development rhythm. You should be making regular process on the development and keeping in close communication with your client to assure that you are on the right trajectory. Team members should be working together to resolve problems and the schedule should be adapted to adjust for changes in your understanding of the functions. A well-functioning team will not be regularly changing their schedule because of members not doing what they are assigned (though this will happen on occasion). Team members should be supportive of one another and helping each other solve technical problems.
Completion Phase: In the last 5 weeks, you need to start making hard decisoins. This is the time that you stop believing that miracles will happen or that you will see the light. You need to be realistic about how much "additional" time you will be able to give to this course. You need to discard items that you are not going to be able to accomplish and focus on polishing the things that you are going to deliver. It is the time to establish expectations with your client. Users need to be giving you feedback and documentation needs to be written.
- The code grade covers function, correctness and readability. The three components are equally important. Have you met the primary requirements? How many bugs was I able to find? I will do a random review of the code that you produce. I expect to be able to understand it. This includes web pages as well as other code that you write.
- The documentation covers the formal deliverables: the functional spec, the design document, the user manuals, and the test plan. They are weighted equally. Remember that spelling, grammar, and readability are important; unreadable good content is not sufficient.
- For the final presentation, your grade will include both content and style.
Your grade will include both content and style. I will be looking to see if you understand what you are presenting and whether you are communicating well with your classmates.
There will be two essays assigned. The intent is to introduce you to the classic literature of the field. Grading will be based on the demonstration of understanding the content, reasonable proofing, and following instructions.