]
]The presentation is for explaining your project (i.e., both the product and the process) to the evaluators. This page assumes a closed-door presentation where only the evaluators will be present.
Presentation complements the report (and the product demo, if any). It gives evaluators a chance to clear up doubts about the report by asking on-the-spot questions, for example.
Project presentations are usually scheduled back-to-back, all of which are attended by the same panel of evaluators, and sometimes all the teams present the same product. Needless to say evaluators get irritated when you run over the time limit. It shows gross negligence on your part; if you did a rehearsal, you should have realized the problem earlier.
Project presentations are usually short. Shorter the presentation, more the amount of practice you need. Use the time wisely, do a couple of practice runs. Perfect your delivery. Sometimes things you intend to say sounds clever in your head, but come out lousy when you actually say it aloud.
Be prepared for questions you can anticipate. Even if you have done all the right things in your project, evaluators get suspicious if you cannot explain the rationale behind your decisions. Let your team mates ask questions (that are likely to be asked by evaluators) during rehearsals, and make sure you can handle them fluently.
Don't waste time on what is obvious. For example, don't waste a slide to explain what is unit testing; evaluators know what it is (you might inadvertently display your own lack of understanding of unit testing! I've seen that happen) Mention them in passing if you must. Instead, focus on what is unique in your project.
If you think a top-notch sales pitch can cover up a lousy project, you are mistaken. Give a balanced view of what happened. Talk about things that went right, as well as things that went wrong (and why they went wrong, what is the lesson learned etc.). Experienced evaluators are quick to see through the marketing-oriented presentation that oversells the project.
For some members of the evaluator panel, presentation is the sole means of evaluating your project (not all evaluators can read all reports). Do not underestimate its importance.
Any suggestions to improve this book? Any tips you would like to add? Any aspect of your project not covered by the book? Anything in the book that you don't agree with? Noticed any errors/omissions? Please use the link below to provide feedback, or send an email to damith[at]comp.nus.edu.sg
 |
Sharing this book helps too! |
---| This page is a part of the online book Tips to Succeed in Software Engineering Student Projects V1.9, Jan 2009, Copyrights: Damith C. Rajapakse |---