PRACTICAL PROJECT
PROJECT REPORT
Written report
The report is basically a large version of a normal report, with some extra sections. The size
of the report should reflect the fact that you have spent the equivalent of around 10 normal
practical sessions doing the project work.
The required sections are:
•
Executive summary – a half-page summary of what you did and what you found [½
page]
•
Table of Contents – listing each section and the start page number
•
Introduction – essentially summarises what information you had before you started
your practical work, i.e. what you found about other people’s work in the topic area;
explain what is important about the analyte(s) [1-2 pages]
•
Procedure – the final version of the method(s) you used, written step-by-step with
enough detail for someone else to repeat your work
•
Results – transcribed into neat tables (raw data to be attached in appendix)
•
Calculations – start with a table of summarising what positive results you got; do not
include full calculations for replicates; provide one fully detailed calculation of
each type of calculation (including the recovery check); this will show that you know
what you are doing, give the final answers for the other replicates in a table
•
Discussion – what you had to do to get things to work (or not work); why things didn’t
work; how your results compared to any known values; what you would do differently or
additionally if you had more time [minimum 2 pages]
•
References – see your Sci. Info Skills notes about the correct way to reference your
work; this is not just a list of books in the library or websites: each reference must be
linked to the introduction and discussion section
•
Appendix – your time/reagent/equipment use logs; raw data; daily record sheets
The suggested page lengths provided for some sections should not be treated as maximum
lengths (except the Exec. Summary). If you need to write more, do so, but don’t waffle.
There is a simple way to distinguish between what belongs in the Introduction and
Discussion. You should treat the Introduction as though you wrote it before you began the
practical work, so nothing that relates to your results should go in it. The Discussion is where
your work belongs, but you can still use other people’s work there also.
It is compulsory to prepare your report on computer.
The report is to be handed in after you make your presentation to the class (see below). You
may email your written report, but the Appendix of paperwork should be submitted in that
form – do not attempt to scan it all for email, as you will overload my Inbox, and the system
will complain.
It will be assessed on the following:
• content – what you actually write, including the calculations and especially the
Discussion
• organisation – how well it meets the above requirements
• presentation – marks will be deducted for poor, inappropriate or inconsistent formatting
Powerpoint presentation
This MUST be submitted at least ONE day before the presentation session. If you do
not meet this deadline, you will not be allowed to present your report, and hence will not be
able to pass the subject (no exceptions).
It will be loaded onto the computer (with data projector) in the room where the presentations
are held.
There will be some samples of good and bad presentations provided on the subject webpage
which should be considered along with the following things to avoid:
•
irrelevant graphics
•
distracting backgrounds/transitions/animations/sounds
•
the full procedure
•
raw data
•
small text
•
exotic, illegible fonts
It is recommended that a projected slide show employs a light background with dark text, as
this displays better.
Make sure you test your PPt before submitting it. It can be emailed or brought on USB drive.
Verbal presentation
A session in the last week of Term 4 will be set aside for your presentations.
Date: Friday November 30 starting at 9.30 am in E2.8 (be there by 9.20 am)
The order of presentation will be determined by a random drawing of numbers. Anyone
arriving late will go last (the worst position).
You should aim at 10-15 minutes. While this sounds a lot, it isn’t really. It should cover
everything in the written report, but in an abbreviated way.
Do:
•
•
•
•
•
•
try to speak to the class, rather than just read
outline what methods were used
explain the importance of the analyte(s)
show a table and/or graph of the results (not data) that were obtained
calibration graphs are OK to demonstrate linearity (or lack of), but are not essential
explain what went wrong and right and why
Don’t:
•
read your written report – prepare a separate speech version
•
overwhelm with detail (especially data and procedural)