Midway through your project coding, we'd like a brief status report. If you think we're trying to check up on you, you're right; we are, but in a good way. If everything is going fine and you're on schedule, you need only say so. If problems have arisen and you've fallen behind schedule, let us know, and tell us what your new schedule is and how you're planning to remedy the problem.
This is not a graded assignment, and there will be no penalty if you report that you've fallen behind. However, the coding phase is graded, and so it's to your advantage to let us know if there are problems while there's still time to correct the problem. We will be far more upset if we don't find out that there are problems until just before the coding is due, when there's no time to fix it.
This is also a good time to get together with your partner (if you haven't already), to check on how each other is doing. Some groups work very autonomously, which can be good, but it can work out badly if one team member has fallen behind and her partner doesn't know it.
Some of the biggest challenges of doing a big project in a group are coordinating with your partner and staying on schedule; learning how to do this is an important part of why we use group projects in this course.
So, don't let this assignment stress you out. It's only here to help.
What To Do
Email your advisor with a few sentences or paragraphs, saying whether you're meeting the schedule as you put it in your design document. If all is well, this need not be more than a sentence saying so. If your plans have gone awry, as they so often do, say so and say what you'll do to get back on track. In particular, say what isn't done, and a schedule for getting it done by the coding deadline.
We only need one email per team, but please cc your partner on the email so that we know both of you are in agreement with the status.
Introduction | Syllabus | Assignments | Documentation | Project
Computer Science 110Date Created: April 9, 2003