Weekly Report on Project Status
Course: CS3302 (Spring 1996)
Week ending: (mm/dd/yy)
This report should be filled out by the Project Manager and a printed
version should be brought to
class for any status meetings. In addition, you should keep a copy of
this status report on-line and accessible from your project notebook.
This status report will be collected by the instructor/TA and kept as
a record of progress throughout the quarter.
Group Name:
Group Members
| Name |
Role |
Attendance |
| Name 1. |
Role(s) |
|
| Name 2. |
|
|
| 3. |
|
|
| 4. |
|
|
| 5. |
|
|
| 6. |
|
|
Progress
Insert your updated project schedule here. This table should reflect
actual time spent on project activities and when deliverables were
actually turned in.
After the table, list any significant accomplishments since the last
status report. This can include the completion/revision of project
deliverables.
Problems
List any problems the team is having that you would like to discuss.
This includes things that have caused delays, or any other roadblocks
to anticipated progress.
Plans
List your project team's plans for the next week.
Other Comments
Include here any items not covered above that you want to record.
Project team remarks
In this section, you can record any significant items/advice that came
from your status meeting with instructor/TA. This section is not
filled out prior to the status meeting. Instead, it is filled out
after the project to help remind group members of significant items
discussed in the meeting.