Each student is to prepare a Project Debriefing Report. The reports for each project, when put together, will provide a complete overview of the manner in which the project was taken to completion. Please note that submission of the individual assignment is compulsory - no grade will be awarded to students who fail to submit an assignment . Each individual report should contain the following information: Project Description There should be a brief qualitative description of the project in terms of the client, the application, the project team composition, the hardware and systems software used and the software developed. Project History There should be a general overview of the history of the project, highlighting any major factors which influenced the conduct of the project and the management strategies adopted to overcome any problems which arose. A calendar may be included showing delivery dates scheduled and actual for all major project deliverables. Graphical techniques may be used to show progress on the project. In addition, there should be a detailed report on the author's own individual contribution to the project. It should list each task which the author was involved in, showing the deliverables produced, the original estimated time required, and the actual time spent. It should detail individual productivity, in terms of effort required to produce each deliverable; for tasks involving the production of code, the size of each code module should be given in lines of code, excluding comments and an estimate of productivity in lines of code per hour. Please note that assessment will not be based on productivity, time spent or the effectiveness of individual contributions to the project; rather, the level of detail provided within the overall space constraint will be a major assessment factor. Evaluation of Techniques and Systems There should be a qualitative judgment of all the techniques and systems used, including: the hardware and systems software; methods and tools used in each of the phases; project team structure; monitoring and reporting methods; and client liaison and change control methods. The evaluation should take into account the effect of the systems and techniques selected on project productivity and product quality. General Words of Wisdom This section may include any matters affecting the conduct of the project which do not fit readily elsewhere in the report. This could include problems with acquiring necessary hardware or software, internal problems within the team, etc. It could include thoughts on how to run the project if it were to be repeated. It should incorporate any suggestions on ways in which the course itself can be improved. Peer Evaluation Report A Peer Evaluation Questionnaire will be distributed to all students late in second semester. It must be completed and returned with the assignment. Failure to do so will be treated in the same way as failure to submit the individual assignment - i.e. no grade will be awarded. Original Author: Terry Rout Redesigned: 12 October, 1996 by Tracey Osborne Last Updated: 15 July , 2001 by Jenine Beekhuyzen Send comments, errors and suggestions to Angela Tuffley, projects@cit.gu.edu.au