This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
presentations:tips [2006/03/12 14:53] 70.237.140.143 Created from a checklist I created several years ago. (CMB) |
presentations:tips [2012/12/09 19:36] (current) SLUUG Administration A few updates. (CMB) |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== Checklist for Presentation Speakers ====== | ====== Checklist for Presentation Speakers ====== | ||
+ | I started writing this up partly for myself, as I learned how to give presentations. I then adapted it to give some advice to those who are not experienced giving presentations, and to set some expectations for those who speak to our group. These are definitely not hard and fast rules -- some of the best presentations we've had have been completely different. But if you're a beginner, try to stick pretty close to these guidelines. | ||
+ | --- Craig Buchek | ||
+ | |||
+ | There are some other helpful guidelines available from the [[http://www.slug.org.au/meetings/guide.html | Sydney LUG]]. | ||
- Be knowledgeable about the subject you are speaking on. | - Be knowledgeable about the subject you are speaking on. | ||
Line 6: | Line 10: | ||
* Be prepared to answer tough questions. | * Be prepared to answer tough questions. | ||
* People may challenge you on technical details. | * People may challenge you on technical details. | ||
+ | * COUNTERPOINT: It's also cool to talk about something that you just learned. | ||
- Know your audience. | - Know your audience. | ||
* The topic should be relevant to a technical audience. | * The topic should be relevant to a technical audience. | ||
Line 13: | Line 18: | ||
* Some may be experts and know more than you do. | * Some may be experts and know more than you do. | ||
- Figure out what you want to talk about. | - Figure out what you want to talk about. | ||
- | * Come up with a high-level outline, about 4 to 6 bullet points. | + | * Come up with a high-level outline, about 3 to 6 bullet points. |
- | - Submit the presentation title, an abstract, and a bio promptly. | + | - Submit the presentation title, an abstract, and (optionally) a bio. |
- | * Email it to ''presentations'' at ''sluug.org'' | + | * Email it to your SLUUG contact. |
- | * This info is needed about 2 months before your presentation. | + | * The sooner we can get this info, the better. |
* So we can get the word out so interested people will attend. | * So we can get the word out so interested people will attend. | ||
+ | * So we can update the web site(s) with info on what the topic will be. | ||
* The abstract briefly says what you will talk about. | * The abstract briefly says what you will talk about. | ||
* A paragraph to introduce the topic. | * A paragraph to introduce the topic. | ||
Line 32: | Line 38: | ||
* They can make arrangements to get equipment. | * They can make arrangements to get equipment. | ||
* Let them know of your progress and any problems. | * Let them know of your progress and any problems. | ||
- | * Have them review the presentation if possible. | + | * Have them review the presentation, if possible. |
- Arrange to make sure you will have the equipment you need. | - Arrange to make sure you will have the equipment you need. | ||
- | * We generally have access to a VGA projector, which does 800x600 natively. | + | * We generally have access to a VGA projector, which does 800x600 or 1024x768 natively. |
- | * We usually have access to a whiteboard. | + | * We usually have access to a whiteboard. (Markers, on the other hand...) |
+ | * We usually have WiFi Internet access. | ||
* Please ask if you need any additional equipment. | * Please ask if you need any additional equipment. | ||
- | * Bring a power strip. | ||
* External mouse and keyboard are handy if you use a notebook. | * External mouse and keyboard are handy if you use a notebook. | ||
- Prepare your presentation. | - Prepare your presentation. | ||
* Structured presentations are preferred, but not required. | * Structured presentations are preferred, but not required. | ||
+ | * Hand-outs usually go over well. | ||
+ | * Even as a substitute for slides. | ||
* Slide presentations with bullet-points work very well. | * Slide presentations with bullet-points work very well. | ||
* Figure on about 5 minutes per slide. | * Figure on about 5 minutes per slide. | ||
Line 52: | Line 60: | ||
* Make sure you undo the effects of any practice runs. | * Make sure you undo the effects of any practice runs. | ||
* Test with the same versions that you will demo. | * Test with the same versions that you will demo. | ||
- | * Disconnect any network connections when testing. | ||
- | * You probably won't have any network at the presentation. | ||
- Arrive early enough to set up and test any equipment. | - Arrive early enough to set up and test any equipment. | ||
* UNIX (Wednesday) meetings start at 6:30 pm. | * UNIX (Wednesday) meetings start at 6:30 pm. | ||
- | * Arrive before 6:15 for tutorial, 6:50 for presentation. | + | * Arrive before 6:20 for tutorial, 6:50 for presentation. |
* Tutorial runs from 6:30 to 7:00. | * Tutorial runs from 6:30 to 7:00. | ||
* Presentation runs from about 7:30 to 8:45. | * Presentation runs from about 7:30 to 8:45. | ||
* Linux (Thursday) meetings start at 7:00 pm. | * Linux (Thursday) meetings start at 7:00 pm. | ||
* Arrive before 6:50. | * Arrive before 6:50. | ||
- | * Presentation runs from about 7:30 to 8:45. | + | * Presentation runs from about 7:15 to 8:45. |
* Be sure you know how to get to the venue. | * Be sure you know how to get to the venue. | ||
- | * UNIX meeting: http://sluug.org/resources/meeting_info/map_graybar.shtml | + | * UNIX meeting: http://sluug.org/resources/meeting_info/map_graybar.shtml ([[http://www.graybar.com/ | Graybar]]) |
- | * Linux meeting: http://www.stllinux.org/directions/ | + | * Linux meeting: http://maps.google.com/maps?q=4633+World+Pkwy+Cir+63134 ([[http://www.itenterprises-stl.org/ | IT Enterprises]]) |
- Be prepared for equipment failures -- they can and do happen. | - Be prepared for equipment failures -- they can and do happen. | ||
* Live demos are good, but are more prone to these problems. | * Live demos are good, but are more prone to these problems. | ||
+ | * Have a backup plan. | ||
+ | * Have your presentation on the Internet and a USB key. | ||
+ | * So you can use someone else's laptop if necessary. | ||
- Hand-outs of the presentation and other resources can be useful. | - Hand-outs of the presentation and other resources can be useful. | ||
* Make sure you have enough for the entire audience. | * Make sure you have enough for the entire audience. | ||
Line 89: | Line 98: | ||
* Don't be afraid to admit that you don't know an answer. | * Don't be afraid to admit that you don't know an answer. | ||
* Ask if other audience members might know the answer. | * Ask if other audience members might know the answer. | ||
+ | * If the presentation doesn't lend itself to interruptions, take questions at the end. | ||
+ | * State up front whether you want questions at the end or during the presentation. | ||
- Be prepared to shorten (or lengthen) the presentation. | - Be prepared to shorten (or lengthen) the presentation. | ||
* Put some optional stuff at the end. | * Put some optional stuff at the end. | ||
Line 99: | Line 110: | ||
- If possible, submit your presentation to put on our web site. | - If possible, submit your presentation to put on our web site. | ||
* Submit HTML and native format if possible. (Any format is OK.) | * Submit HTML and native format if possible. (Any format is OK.) | ||
- | * Email your presentation to ''presentations'' at ''sluug.org'' | + | * Email your presentation to ''editor'' at ''sluug.org'', or your contact. |
+ | - Some of us go to dinner after the meetings. | ||
+ | * Join us there for additional conversation, if possible. |