Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: minor

...

  1. If it's a short time slot, keep corporate introductions to a minimum.  Get to the meat of the topic.
  2. Present the technical challenge in question (and if the talk abstract already presents it, this too can be short, but you might prefer to highlight a particular aspect)
  3. Then present solutions.  Do not be afraid to be opinionated here, since RoE sessions are for "several companies unique view on a subject".
  4. We have a technical audience and this is not a "business track".  Some tips:
    1. You can use the opportunity to describe several possible approaches
    2. Include criteria for choosing one method over another, whether based on practical tryouts, or on theoretical reasoning,
    3. ... try to include hard data, which is useful to guide a technically minded audience:  Measurements, statistics, memory footprint, size, lines of code, performance benchmarks, and so on. 
    4. Finally, including negative experiences, mistakes, or reasons why an alternative did not work out, is also extremely useful for everyone.  Please remember that these sessions are about sharing of real-world experience!
  5. When possible RoE focuses on production experience.  If applicable, mention experiences from putting the solution into production cars. 
  6. Finally your company is of course free to take this opportunity to mention a solution you may have in your portfolio (i.e. a solution to the presented challenge, not other irrelevant products).  As you can see, the presentation is not expected to be a plain "sales pitch" – it ought to explain technical rationale for the offered product, and the rest of the presentation material should overall add to the shared body of technical knowledge.
  7. There is often a single shared abstract, but while considering that description and the above tips, you may still interpret the topic quite freely.
  8. If the shared abstract totally does not match your speaking intentions,  let us know and we should discuss it.
  9. There might not be time for Q&A, but for some topics we have related workshop time, where we can follow up on what was presented with audience interaction (note there is a schedule for each workshop, so make sure there is time planned for this). 
    To unify the presenters' approach, let's use this guideline for speaker slot length:
    =< 20 minutes  –> no Q&A
    >20 minutes**  -> optional Q&A, speaker decides (but stay within allotted time)

...