Better Presentations (English)

Experienced developers and architects often have to present their ideas and topics to various audiences ranging from technical team members to critical management. This session adresses basic techniques for presentations and a simple, easy to follow process for creating better and more convincing presentations. The topics that we'll cover range from analyzing your audience, basic argumentations techniques to slide design.

Transcript

1. Better Presentations
2. Michael Plöd Partner and Principal Architect at Senacor Technologies AG More than 50 (conference) talks Author Java Magazin @bitboss http://speakerdeck.com/mploed
3. Dear developers, I don‘t want to drag you to the dark side of the force
4. There are far too many bad and boring presentations
5. Also I started with bad presentations
6. Bad Design
7. No Message
8. Bullet Point Bonanza
9. Bad Delivery
10. PowerPoint Material- search The usual process consists of only 2 Steps Bad Presentation
11. Good Presentation Arguments Design Delivery
12. Everyone can create good Presentations...
13. ... if you follow a simple process...
14. Five simple steps ......
15. Step 1: Analysis of audience
16. Step 2: Material collection
17. Step 3: Argumentation
18. Step 4: Layout
19. Step 5: Delivery
20. In the beginning we work Analog
21. Step 1: Analyze the audience
22. The speaker is not the Hero
23. The audience is the Hero
24. 7simple questions for analyzing the target audience Source: Nancy Duarte - Resonate
25. What moves them?
26. How can I solve their issues?
27. What do I want my audience to do?
28. Who are they?
29. Which resistance will I get?
30. Why are they here?
31. How can I reach them?
32. Analyze the environment as well
33. Step 2: Material collection
34. Collection of ideas with pen and paper OFFLINE
35. Example: Collection of ideas
36. Collection Selection Assessment
37. Fist: Collect without restrictions N+1 Problem 2nd Level Cache Batch Fetching Lazy Loading Eager Fetching Karthesian Product Hibernate Statistics Ignore Bind Variables Log Files for Queries Subselect Fetching Query Cache Session and 1st Level Cache
38. Log Files for Queries Then: Group N+1 Problem 2nd Level Cache Eager Fetching Karthesian Product Hibernate Statistics Ignore Bind Variables Subselect Fetching Query Cache Session and 1st Level Cache Lazy Loading Batch Fetching Fetching Strategies Problems Analysis Caching
39. Log Files for Queries 2nd Level Cache Hibernate Statistics Query Cache Session and 1st Level Cache Eager Fetching Subselect Fetching Lazy Loading Batch Fetching Fetching Strategies There are 2 main issues There are 2 tuning spots Caching Tools Finally: Messages N+1 Problem Karthesian Product
40. Step 3: Argumentation + Story
41. Each presentation has one Main Message It is the minimum take away of your audience
42. Inductive Reasoning Message Answer Answer Answer Question
43. Inductive Reasoning Everyone can create good presentations Process Argumentation- techniques Design Basics why?
44. M E C E utually xclusive ompletely xhaustive
45. ME CE Message Message Messages don‘t overlap with regards to their content Answers are sufficent to make the message intangible
46. Deductive Reasoning Message Neutral Claim (Situation) Commenting Claim (Complication) Conclusion from Situation and Complication why? +
47. Deductive Reasoning Test of project xyz should be suspended for 2 weeks There are many bugs in the current test release The bugs prevent a smooth business test Hence the test should be paused for 2 weeks in order to enable the developers to fix the bugs why? +
48. Inductive and deductive reasoning can be combined +
49. Deductive with inductive reasoning +
50. Complete inductive reasoning
51. What do those guys have in common?
52. ! a great Story
53. Ethos Pathos Logos
54. Based on our reasonings we create a Storyboard
55. What is? What can be? A Sparkline helps us to structure the story
56. What is? What can be? The STAR-MOMENT is the highlight of your presentation
57. Step 4: Layout + Design
58. Initial layout of ideas with pen and paper OFFLINE
59. Example: Layout
60. 3simple rules for a great slide layout
61. One message per slide
62. Keep it simple
63. Use graphs instead of words
64. Visualization of Data
65. Presentation software offer too many types of charts 0 25 50 75 100 2007 2009 0 50 100 150 200 2007 2009 0 25 50 75 100 2007 2010 0 17,5 35 52,5 70 0 25 50 75 100 2007 2009 7 % 8 % 10 % 11 % 29 % 35 % 0 10 20 0 5 10 15 20 2007 2008 2009 2010 0 50 100 150 200
66. Categorize messages in Comparison Types Structure Frequency Time Series Context Ranking
67. A structural comparison contains procentual or proportional information in the message 27% of the reported errors were in the user interface whereas only 4% could be allocated to the business logic 9 % 60 % 4 % 27 % UI Business 3rd party libs Other
68. A frequency comparison aims to show how often a figure appears in different magnitudes Most of the bugs are CSS layout bugs 0 15 30 45 60 DB JS CSS Java
69. A time series comparison documents the change of a figure over a certain amount of time „We managed to lower our build times by 45% within the last 30 weeks by introducing Gradle “ 0 25 50 75 100 0-10 10-20 20-30 AVG Build Time
70. A contextual comparison displays data in context to each other an aims to deduce correlations „Too many queries are executed too often in relation to their runtime“ 0 100 200 0 100 200
71. A Ranking evaluates data in order to deduce a order of precedence „Most of the developers in our team favor Apache Wicket whereas JSF is not very popular“ 0 15 30 45 60 JSF GWT Wicket
72. Visualization of textual facts with Slides
73. Structure Display of structure within layers, trees or a matrix
74. Cluster Display of grouped information
75. Flow Display of processual flows
76. Radiate Display of correlations, knots and cores
77. Influence Display of cause and effect
78. Don‘t manipulate
79. Step 5: Performance
80. Senacor Special Print Open Source Integration magazin Java t Architekturen t Web t Agile www.javamagazin.de CD-INHALT JAVA Mag 12.2011 Lean Enterprise Architecture Video von der JAX 2011 HIGHLIGHT Death of XP Java Tech Journal Special Edition EXKLUSIV für unsere Leser WEITERE INHALTE r
    -VDFOF
    
    4PMS
     r
    "DUJWF.2
     r
    $9'
     Soft Skills konkret Effektiv vermitteln, aber wie 97 Geoinformations- systeme Orte malen 86 Brandneues Programm 51 Best Practices mit Git Besser Gits nicht! 100 Solr unter Strom Suchmagie für Applikationsentwickler 48 Apache Cayenne Mit Remote Objects Welten verbinden 30 Googles JPA: Bigger Table, lesser Standard? 80 Integration HIGHLIGHT Death of XP Java Tech Journal r
    "DUJWF.2
     r
    $9'
     Best Practices mit Git „Präsentationstechniken für Softwareentwickler und -architekten“ von Michael Plöd, Principal Architect und Partner bei Senacor Technologies AG 4POEFSESVDL
    t
    4POEFSESVDL
    t
    4POEFSESVDL
    t
    4POEFSESVDL
    t
    4POEFSESVDL
    t
    4POEFSESVDL
    t
    4POEFSESVDL
    t
    4POEFSESVDL
    t
    4POEFSESVDL
    t
    4POEFSESVDL
    4POEFSESVDL
    t
    4POEFSESVDL 4POEFSESVDL
    t
    4POEFSESVDL
    t
    4POEFSESVDL
    t
    4POEFSESVDL
    t
    4POEFSESVDL
    t
    4POEFSESVDL
    t
    4POEFSESVDL
    t
    4POEFSESVDL
    t
    4POEFSESVDL
    t
    4POEFSESVDL
    4POEFSESVDL
    t
    4POEFSESVDL E-Book
81. Thank you !!! Photos / Graphics (c) Michael Plöd / Senacor Technologies AG Exception: Photos of Michael Plöd (Slides 2, 5) (c) Matthias Heyde Pointy Font licensed from Bitfoundry michael.ploed@senacor.com @bitboss http://speakerdeck.com/mploed http://www.senacor.com