MAKERERE

P.O. Box 7062 Kampala, Uganda Cable !"#KU$%K#& (eb )*e: www.mak.ac.ug _________________________________

UNIVERSITY
Tel: +256 41 531046 'ax: +256 41 531046 e+ma)l: eedep*,*e-..ma/.a-.0g ________________________________

DEPARTMENT OF ELECTRICAL AND COMPUTER ENGINEERING

Final Year Project Presentation Guidelines

This handout has been prepared to give basic guidelines on the final year project presentations. It is expected that students will work closely with their supervisors and hence these guidelines are to be considered supplementary to guidelines from supervisors. Do consult with your supervisors to establish the content and style of your own particular presentation.

1. Presentation Format Presentations are expected to be clear and short. tudents will have !" minutes of presentation and # minutes of $uestions to present their projects. The following will be re$uired of each presentation% &ou must have a visual aid. The visual aid could be a chart' a device you have constructed' a screen shot' a demo' power(point slides or anything else that you might use to help make the presentation concrete. )ll members of the project group must participate in presenting. It is recommended that students time and practice their talks so that they are able to complete the presentations on time. *or example' a rough guide is to expect to spend a minimum of about +" ," seconds per power(point slide- and this should enable you determine the appropriate number of slides for a !"(minute power(point presentation. .sing headings of your choice' your presentations would be expected to address the following issues% /rief /ackground of the Project 0including ignificance12ustification3 Problem tatement 4bjectives 05eneral and pecific3 Project cope 6ethodology 0including stepwise account of process1methods1flow diagram used to accomplish your specific objectives3 7ey 8esults Interpretation1)nalysis of 8esults )reas of Improvements19hallenges *aced1/udget1:ork plan18eferences 0as appropriate3 9onclusions and 8ecommendations 0in line with each of your specific objectives3

2. Tips on preparing your presentation ome $uestions that might help you reflect and guide you in developing your presentations include% Does the presentation tell a coherent story? It;s not essential that the presentation have all the answers or everything complete' but the story should flow. How does the visual aid assist in the explanation? &our visual aid should assist you in telling your story. Do the findings/results/conclusions follow (some how) from the title and content of the presentation? Is there any self-reflection on the project? Did the project members think critically of the directions1decisions< Is there ac nowledgement of what wor ed (what is going well) and/or what did not wor (what is not going so well)? Is there a clear rationale for the decisions? &ou might be forced to make 0what would seem3 an arbitrary decision 0say about a design' an implementation issue or almost anything3. Did you =flip a coin; or is there any reason behind the decision< How much emphasis was placed on the project over the course of the year? Does the depth of the content1result demonstrate an e$uivalent amount of insight1effort< How is the pro!lem addressed !y the project a "computer/electrical/telecommunications engineering# pro!lem? :hat makes this problem interesting from an engineering point of view< How do the results of the project !uild on existing wor $ and contri!ute to future research directions? :hich work1results from past projects was useful to you< :hat still remains to be done and could be taken up as future project ideas< How does the project represent an improvement? >ow do you know you;ve made a difference<

3. Tips on delivering your presentation :hat makes for a good presentation delivery is an important element of this. ome pointers to note include% *irst establish a rapport with the audience ( at the very least greet the audience. Introduce yourself and your supervisors but only briefly as you are already known. 0*or purposes of your presentations' panels will have details of who is presenting what topics. >owever' it is still useful to have an introductory slide which has your name on it.3 .se appropriate words' terminology and jargon. If you think you have used a technical word without explaining it' then pause to explain it. Don?t talk down and don?t talk up. 6ake sure everyone can hear you ( speak to the person on the back row' speak clearly and reasonably slowly.

.se intonation in your voice to add colour and interest. /e expressive. .se the presentation aids 0projector' pointer' etc.3 ( well@ Astablish eye contact with the audience ( but don?t threaten them. P8AP)8A your talk.

:hat not to do when delivering your presentations what makes a bad speaker< Pointers that indicate a bad speaker include% Talks too slowly. The talk is at the wrong level 0either too simplistic or too difficult3. tands still and just talks. There are no visual aids ( or even worse there are poor visual aids. >as a monotonous voice. Bot responsive to the audience. *lippancy@ tares at the projector and1or slides' avoiding eye contact with the audience. Poor timekeeping. 9asual1untidy dressing. 6ore on the issue of flippancy% ometimes students try to hide their inability to give a good presentation through the use of casual and repeated flippancy. Their attitude is one of ( well you all know me' and I know you' and after all this is just a game' so what is the =big deal;' now where?s that slide' oh I can?t find it' never mind it wasn?t important' here?s the next one' well it speaks for itself' most of you know this' so I?ll take it off before you can read it' is the time up yet< no' oh I?ll go on then' etc.' etc.' etc. 8emember that this is an assessed part of your degree' approach it seriously and responsibly ( don?t be flippant. *inally' never answer a $uestion with CI was told to do this by D' & and EC 0usually where D is your supervisor@3. This is your project' your work and your presentation ( accept the responsibility that goes with the position. &ou may well have been CtoldC to do something but in answering a $uestion you should give the reasons that underlay that CtellingC. Don?t pass the buck@ )nswer the $uestion@

4. Concluding remarks These guidelines are not a definitive set of do?s and don?t?s but just some pointers that might help improve the $uality of your presentation. 9hoose the points that you think are relevant or appropriate.

dapted !rom"
P1e en*a*)on 20)del)ne , 3a4)d "-3onald + .**p:55p1o6e-* .) -.ool.7a .)ng*on.ed05m-donald5-o01 e 5)n8o490:7)065page25page2..*ml P1o6e-* P1e en*a*)on 20)del)ne ; .**p:557eb e14)-e .- .no**.a-.0/5)n*1ane*5)ndex.p.p5g0)de +and+.andboo/ +ma)nmen0+<250g+.andboo/+ ma)nmen0+<75 *0d=)ng+a*+no**)ng.am5*.)1d+=ea1+p1o6e-*5<2 23rd April 2010. Revised 10th May 2013