PRESENTATION ADVICE (COMPUTER SCIENCE)

                     COMPUTER SCIENCE                                        PRESENTATION ADVICE

  

 It is also good to give the presenter some practice answering audience questions.

Nervousness: How to fight back

A well organized, practiced talk will almost always go well. You should have the following main sections in your talk:

Introduction, the big picture: what, why and why we should care, and how. Immediately after the title slide, put up an outline slide and tell the audience the main organization of your talk. Your slides are a guide for your talk not a word-for-word copy of your talk.

 Use phrases rather than complete sentences and use large fonts. It is okay to pause for a few seconds between points and between slides; a second or two of silence between points is noticeable only to you, but if you are talking a mile a minute everyone will notice.

Bring notes. The exception is for well-known acronyms such as PVM, MPI, API, JVM, etc.

A picture is worth a thousand words
Use figures and graphs to explain implementation and results. Use good transitions from one slide to the next, and from one main topic to the next..."We just talked about the implementation. The red curve shows the execution time of A as the number of nodes increases.

Thus you can see that as the number of nodes increases above N, algorithm A performs better. Another alternative is to first have a few slides motivating the general topic, and then put up an outline slide giving the audience a road-map of your talk.

It should be clear when you start a new high-level part of your talk. Similarly, if your create an acronym for your super fast multi-cast implementation, SFMC, and refer to the old slow multi-cast implementation as OSMC, then say "our super fast multi-cast" and "the old slow multi-cast" rather than "SFMC" and "OSMC". if you are afraid that you will forget a point or will forget your elegant transition between slides 11 and 12, write these down on a piece of paper and bring it with you. It is very hard to describe a system implementation without having a picture of the components of the system.

Number of slides

As a general rule, it should take 2-3 minutes to talk through the material on one slide, so for a 30 minute talk you should have about 13 slides.

If there are too many ideas in your work to present completely in 30 minutes, then pick one or two (the most interesting/important parts) that you will discuss in detail, and present the other parts at a higher level. You can use acronyms and abbreviations sparingly, however you should say the complete name when you talk about about them.

 After the presenter is done with his/her practice talk, you should talk through the things you wrote down. Be sure to include:

a statement of the problem being solved (what)
motivation and putting the work in context (why and why should we care)
a high-level view of the solution (how)
Details of solution
Results demonstrating your solution
Critiques of the work (possibly compare to related work)
Conclusions and future directions for this work
The talk should be organized so that the important ideas are presented first, the details second, and the conclusions last. Before you give the talk, think about what questions you are likely to get, and how you would answer them. Don't stop and fix slides as you go and don't let your audience ask questions or suggest fixes until your practice talk is over; you want to force yourself to talk through your entire talk.

You should assume that there will be about 5-10 minutes worth of questions during or after your talk. You don't have to know the answer to every question, however you should be prepared to answer questions about your work. You may want to have back-up slides ready for answering certain questions.

It is okay to say "I don't know" or better yet "gee, I hadn't thought about that, but one possible approach would be to..."

Other oral presentation advice:

Mark Hill's oral presentation advice

Jim Marshall's oral presentation advice

Ian Parberry's "How to Present a Paper in Theoretical Computer Science". irst, organize your talk:

Identify the important ideas

Your work (or the work you are presenting) likely has many details, but only one or two main ideas; structure your talk around these main ideas.

Create a talk outline
Your talk should be organized in a top-down manner. If applicable, Include a list of open questions and/or future directions of your work.

It is okay to waste space
Add just enough prose prose to present the main points and highlight the main parts of each point. Now we will look at how well the system performs."
You may want to use the outline slide at other points in your talk to provide a visual transition between parts of your talk.

Repeat your point

There is a rule that says you have to tell your audience something three times before they really hear it:

Tell them what you are going to say.
Say it.

Summarize what you said.

This is particularly important for figures and graphs. Take a few seconds to think about a question that is being asked before you answer it. For example:

This graph show how algorithm A performs better than algorithms B and C as the number of nodes increase.
The X axis is the number of nodes, the Y axis is the execution time in seconds. This is because...

Talk to the audience

Don't read your slide off the computer, nor directly off the screen. Each section of your talk should be organized in a similar manner: big ideas, details, then summarize.
Next, design your slides:

Slide organization
Your slides should be organized like an outline--a few main points, with sub-points under each one. One trick is to try to remember to take a deep breath between each slide.
Slow down. It is okay to stop for a second and refer to your notes if you need to.
Practice
Give a practice run-through of your talk in front of an audience of at least one other student. For example, if you abbreviate processes to procs on a slide, say "processes" when you talk about the point not "procs". Also, you can create back-up slides for specific details that you don't plan to talk about, but may get questions about.
Then, prepare your presentation:

Provide a talk road-map

Tell the audience where you are going with your talk.
Give audience a road-map of your talk at the beginning by using outline slides. If your talk is too long, you should cut out some material to get it to fit into the time slot (your audience will not mind if your talk ends 5 minutes early, but they will mind if it goes 5 minutes over).

As a practice talk audience member, you should jot down notes of places in the talk where you have suggestions for improvements, or where something seems unclear. This should be a timed dress rehearsal. If you draw a blank, then looking at your slides will help you get back on track.

Taking a deep breath will clam you down. Stand in a room for 30 minutes (or the duration of your talk) and talk through all your slides (out loud). If there are particular details that you want to discuss, outline them on the slide and keep written notes for you to refer to in your talk rather than writing all the details on the slide.

Summarize main points
You should have a summary slide of the main ideas at the end. However, you don't want to have a verbatim copy of your talk, instead write down key phrases that you want to remember to say.

Be prepared to answer questions. List specific points that you want to talk about as sub-topics of each main topic.