Presentation Skills Workshop

Workshop from 2016 run by DDD Brisbane organisers

Transcript

1. PRESENTATION SKILLS WORKSHOP DAMIAN BRADY - @DAMOVISA BRONWEN ZANDE - @BRONWENZ DAVID COOK - @DAVID_COOK CHRIS GILBERT - @CHRISWITHPANTS
2. WHAT? • Choosing a topic balancing your interests and expertise with what people want to see • The submission process how to get your submission noticed and get on the agenda • Structuring your talk keeping people interested throughout • Presentation techniques getting your message across in a memorable way
3. WHY? • More submissions • Better submissions • More diversity
4. WHY WOULD I EVEN?
6. Commit then learn
7. Respect the audience
8. CHOOSING A TOPIC BALANCING YOUR INTERESTS AND EXPERTISE WITH WHAT PEOPLE WANT TO SEE
9. CHOOSING A TOPIC Passion Expertise ☞
10. CHOOSING A TOPIC • Keep notes • Pay attention to other talks
11. TITLE AND ABSTRACT HOW TO GET YOUR SUBMISSION NOTICED AND GET ON THE AGENDA
12. Follow the submission rules!
13. A TITLE SHOULD… • Get noticed “Using Octopus Deploy” vs “Octopus Deploy or how to stop deploying like an idiot” • Convince people to read more You know what they say about first impressions
14. THE TITLE • Explain what you’ll show • Explain a problem • Target your audience
15. COMMON SUCCESSFUL PATTERNS Building {a thing} [with {a technology}] Building a conversational user interface Building Maintainable Software Build your own Marketplace: Online Payments Building Droids with JavaScript Building APIs with MVC6 and OAuth
16. COMMON SUCCESSFUL PATTERNS {doing a thing} Thinking in React Thinking like a hacker Let’s build a native mobile app with NativeScript and Angular 2 Designing an API
17. COMMON SUCCESSFUL PATTERNS {a topic}: {a hook} Deploying Straight to Production: A Guide to the Holy Grail The Actor/Model pattern in .NET: Akka.NET vs Orleans for the curious Event Driven Cloud Computing: Azure Functions vs AWS Lambda Back to basics: simple, elegant, beautiful code Making ReSharper Sharper: How to make your own R# plugin
18. COMMON SUCCESSFUL PATTERNS {an interesting question?} What makes React different? What’s it like being an open source maintainer anyway? Panel: What is quality code? Sweet, you’re agile! Now what?
19. AN ABSTRACT SHOULD… • Convince the reader Why see your talk when there are so many others? • Not be aimed at you You already know this stuff – why should I care? • Have an intro for buy-in • Clearly describe what you’ll show • Have a reason to attend
20. THE ABSTRACT • Start with a “why”-based intro • Explain exactly what you’ll do • Explain the exact problem you’re addressing • Make a connection with the attendee
21. ABSTRACT STRUCTURES THAT WORK • Here’s the problem • … is the solution • I’ll show you …
22. ABSTRACT STRUCTURES THAT WORK • Have you wandered about …? • I’ll tell you … • By the end, you’ll …
23. OTHER TIPS • Thank about talks that have disappointed you in the past. Were the abstracts not clear enough about what to expect? • Convince the attendee that your talk is worth seeing. • Look at abstracts for past conferences. Which ones catch your eye? • Avoid Buzzfeed. It doesn’t work online and it doesn’t work here. J
24. QUESTIONS TO ASK YOURSELF • Would I be interested in this if I knew nothing about it? • Do I know why this talk has been written? • Do I know why I should attend this talk? • Do I know what I’ll learn by the end of it?
25. OCTOPUS DEPLOY OR HOW TO STOP DEPLOYING LIKE AN IDIOT Ever had your site go down because Jim accidentally copied over the web.config? Ever broken out into a cold sweat because you forgot the where clause was in a production update script? Well stop deploying like an idiot. Deploying applications has traditionally been one of the most dangerous parts of software development. It’s often very hands-on, relying on the right people doing the right thing at the right time, and is therefore extremely prone to failure. In this presentation, Damian briefly looks at why developers should automate the entire deployment process as soon as possible. He looks at some of the ways teams try to manage their deployments and reduce the danger. Finally, He’ll show you why Octopus Deploy is the best way to do it. Damian will show you some real-world Octopus implementations, including very complex environments, in-depth testing, and automated rollbacks.
26. JUST LET ME DO MY JOB! Working with other people sucks sometimes. You're employed to get things done. So is everyone else in the company. But despite being "on the same team", everyone has their own idea of priorities, urgent tasks, and tasks they consider a waste of time. Different teams and departments have different goals, and when they clash, it slows everyone down and can be frustrating and demotivating. So what's the solution? How can you convince everyone to just let you do your job? In this talk, I'll share some practical changes you can make to help fix this problem. Backed up by both research and personal experience, these tips will help you to avoid frustrations and focus on what you're employed to do. We'll discuss topics like wasteful meetings, interruptions, unplanned work, frequently changing priorities, and menial tasks. From small changes in your own team, to ways to influence large cultural changes, there's something here for everyone.
27. Spend more time on “why” ☞
28. LINKS • Past Agendas • DDD Brisbane • DDD Melbourne • DDD Perth • Blog Posts • What your conference proposal is missing • Conference Prompts: Or How to Submit Proposals and Influence People • What I learned from reading 429 conference proposals • Lessons learned in Public Speaking
29. STRUCTURING THE TALK KEEPING PEOPLE INTERESTED THROUGHOUT
30. You’re not just giving information You’re there to entertain
31. Throughline ☞
32. STRUCTURES THAT WORK • Once upon a time, there was… • He/she/they were ... All the time... • Until one day, ... • So no, it’s better because... • (repeat) • Now, here’s what it looks like for them...
33. STRUCTURES THAT WORK • Here’s a problem you have • Here’s a new solution and why it works • Let’s take a look • (repeat) • Summary + reward
34. Say less
35. PRESENTATION TECHNIQUES GETTING YOUR MESSAGE ACROSS IN A MEMORABLE WAY
36. Practice, practice, practice
37. It’s not a brain-dump
38. Short pitch 1 min, 30 seconds, 15 seconds ☞
39. Presentation style
40. Body language is important ☞
41. COMMON* KNOWLEDGE • One idea per slide • Use pictures that relate to your subject • Don’t write all the words that you’re going to say. It means people will read them rather than listening to you and you won’t get the opportunity to get your point across. • Slide decks are a tool, not a crutch • Don’t use (too many) bullet points!
42. REMEMBERING IT http://waitbutwhy.com/2016/03/doing-a-ted-talk-the-full-story.html
43. DELIVERING IT
44. When things go wrong…
45. USEFUL RESOURCES • The Noun Project • Pexels • Consider paying…
46. DDD BRISBANE • Saturday 3October • Submissions close Friday 7 October! • Let’s do it!