Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Talk to Me Right!

Ce5b219b385d3e316a553d8a41900ed9?s=47 Annyce D.
February 02, 2019

Talk to Me Right!

Software development is challenging because as a technical team, we have to figure out what to do, do it, and then make sure we’ve done it right. And each step requires effective communication. In this talk, we’ll look at various tools and techniques that can help propel your career by making you a more effective technical communicator.

Learn what forms of communication are the most important to automate and which require a personal touch in your team’s daily activities. We’ll also discuss how you can best structure meetings to achieve your team’s goals. Finally, we’ll review some common challenges to effective communication and how you can navigate them successfully.

Our coworkers aren’t all robots yet. Effective communication will continue to play a major role in the success of our teams. So let’s do it right!

Ce5b219b385d3e316a553d8a41900ed9?s=128

Annyce D.

February 02, 2019
Tweet

More Decks by Annyce D.

Other Decks in Technology

Transcript

  1. @brwngrldev Talk to Me Right!

  2. Right? @brwngrldev

  3. @brwngrldev

  4. @brwngrldev

  5. @brwngrldev

  6. @brwngrldev

  7. @brwngrldev 12

  8. Your Turn

  9. @brwngrldev 1 Establish relationships

  10. @brwngrldev

  11. @brwngrldev

  12. @brwngrldev

  13. @brwngrldev

  14. @brwngrldev

  15. @brwngrldev

  16. @brwngrldev

  17. @brwngrldev 2 Have clear guidelines

  18. @brwngrldev

  19. @brwngrldev

  20. @brwngrldev

  21. @brwngrldev

  22. @brwngrldev WORKFLOWS

  23. @brwngrldev WORKFLOWS Planning

  24. @brwngrldev WORKFLOWS Planning Coding

  25. @brwngrldev WORKFLOWS Planning Coding Pull Request

  26. @brwngrldev WORKFLOWS Planning Coding Pull Request CI Checks

  27. @brwngrldev WORKFLOWS Planning Coding Pull Request CI Checks Code Review

  28. @brwngrldev WORKFLOWS Planning Coding Pull Request CI Checks Code Review

    Regression
  29. @brwngrldev WORKFLOWS Planning Coding Pull Request CI Checks Code Review

    Regression Done
  30. @brwngrldev ASSume

  31. @brwngrldev HOW TO:

  32. @brwngrldev HOW TO: • Daily Stand-ups

  33. @brwngrldev HOW TO: • Daily Stand-ups • Ticket Estimation

  34. @brwngrldev HOW TO: • Daily Stand-ups • Ticket Estimation •

    Experiment Design
  35. @brwngrldev

  36. @brwngrldev Use Automation 3

  37. @brwngrldev Source: http://www.alexandra-hill.com

  38. @brwngrldev Source: http://www.alexandra-hill.com

  39. @brwngrldev A Use a constant.

  40. @brwngrldev

  41. @brwngrldev

  42. @brwngrldev CI

  43. @brwngrldev https://youtu.be/1xZHZa1ngo4

  44. Your Turn

  45. @brwngrldev 4 Use Templates

  46. @brwngrldev PRs

  47. @brwngrldev PRs

  48. @brwngrldev Tem plates

  49. @brwngrldev Bug Reports The app crashed unexpectedly. Description:

  50. @brwngrldev

  51. @brwngrldev Bug Reports

  52. @brwngrldev Bug Reports The app crashed unexpectedly. Description: Steps to

    Reproduce: 1. Open the app, wait for data to load. 2. Click on the “Pie” recipe. 3. App crashes. …
  53. @brwngrldev 5 Be explicit

  54. @brwngrldev

  55. @brwngrldev Hey, IF-312 just came in, it’s high priority. Can

    you take a look? A
  56. @brwngrldev Hey, IF-312 just came in, it’s high priority. Can

    you take a look? A Sure, no problem. D
  57. @brwngrldev 2 hours later Hey, IF-312 just came in, it’s

    high priority. Can you take a look? A Sure, no problem. D
  58. @brwngrldev Where are we with IF-312? Is it fixed? A

  59. @brwngrldev Where are we with IF-312? Is it fixed? A

    No, I haven’t started on it yet. Was finishing another task first. D
  60. @brwngrldev A Where are we with IF-312? Is it fixed?

    A No, I haven’t started on it yet. Was finishing another task first. D
  61. @brwngrldev • Define: high priority Be explicit

  62. @brwngrldev • Define: high priority • Provide time-constraints Be explicit

  63. @brwngrldev Be explicit • Define: high priority • Provide time-constraints

    • Check for understanding
  64. @brwngrldev 6 Liberal use of questions

  65. @brwngrldev

  66. @brwngrldev Pull Requests

  67. @brwngrldev Pull Requests • “Why did we want to do

    this here?”
  68. @brwngrldev Pull Requests • “Why did we want to do

    this here?” • “Can you explain the motivation for this change?”
  69. @brwngrldev Pull Requests • “Why did we want to do

    this here?” • “Can you explain the motivation for this change?” • “This line confuses me. Is it meant to queue the work?” • …
  70. @brwngrldev

  71. @brwngrldev 1 on 1 • “What skills would you like

    to develop right now?”
  72. @brwngrldev 1 on 1 • “What skills would you like

    to develop right now?” • “Do you feel we’re helping you advance your career?”
  73. @brwngrldev 1 on 1 • “What skills would you like

    to develop right now?” • “Do you feel we’re helping you advance your career?” • “What are you working on that you wish you weren’t?” • …
  74. @brwngrldev So Far… 1. Establish relationships 2. Have clear guidelines

    3. Use automation 4. Use templates 5. Be explicit 6. Make use of questions
  75. @brwngrldev 7 Read before clicking send

  76. @brwngrldev jeff@mycompany.com My third request… Jeff, This is my third

    request for your feedback on the latest designs! I need to know if users will be trained on the verification process before I can proceed. Designs attached. Karen
  77. @brwngrldev Remix

  78. @brwngrldev jeff@mycompany.com [Action Needed]: Final Agent Verification Designs Hey Jeff,

    We’re working to wrap up the agent verification designs (see attached). Do you know if users will be trained on the process in advance? If you’re not the right person to answer these questions, can you help us out and forward this email along? " Thanks a lot! Karen
  79. @brwngrldev

  80. @brwngrldev

  81. @brwngrldev One of your code changes broke CI, can you

    fix it?
  82. @brwngrldev One of your code changes broke CI, can you

    fix it? Hey, CI is down for the app. I’ve been able to track it down to a recent change, ZS-1822 (link). Would you be able to take a look. It’s currently blocking the QA team. Thanks #
  83. @brwngrldev 8 Have POWERful meetings

  84. @brwngrldev

  85. P O W E R @brwngrldev

  86. Purpose O W E R @brwngrldev

  87. Purpose Outcomes W E R @brwngrldev

  88. Purpose Outcomes What’s in it for them E R @brwngrldev

  89. Purpose Outcomes What’s in it for them Engagement R @brwngrldev

  90. Purpose Outcomes What’s in it for them Engagement Roles and

    responsibilities @brwngrldev
  91. @brwngrldev Purpose: Discuss the various available options for a cross-

    platform mobile solution.
  92. @brwngrldev Purpose: Discuss the various available options for a cross-

    platform mobile solution. Outcomes: Final decision on cross-platform solution documented.
  93. @brwngrldev Purpose: Discuss the various available options for a cross-

    platform mobile solution. Outcomes: Final decision on cross-platform solution documented. Agenda: 5 min: Review the current available options. 10 min: Each person discusses their desired choice and why. 15 min: Decide on final choice and document it. 5 min: Meeting Recap and Summary of Action Items
  94. @brwngrldev

  95. @brwngrldev 9 Use Data for Objectivity

  96. @brwngrldev

  97. Velocity @brwngrldev

  98. @brwngrldev

  99. @brwngrldev Tool Usage

  100. @brwngrldev

  101. @brwngrldev 920 3,506 0 17.5 35 52.5 70 April May

    June 1.70 11% 12% 15% 17% 45%
  102. Your Turn

  103. @brwngrldev 10 Simplify your language

  104. @brwngrldev

  105. @brwngrldev Jira

  106. @brwngrldev Jira In order to support the appropriate validation of

    users we would like to introduce the capability to capture their personal identification document via a photograph taken by means of the device. All superfluous content should be eliminated before uploading the captured photographs.
  107. @brwngrldev

  108. @brwngrldev Jira Allow a picture to be taken of users’

    personal IDs. Each image should be cropped before upload.
  109. @brwngrldev Tips • Use shorter sentences

  110. @brwngrldev Tips • Use shorter sentences • Use everyday words

  111. @brwngrldev Tips • Use shorter sentences • Use everyday words

    • Avoid local idioms
  112. @brwngrldev

  113. @brwngrldev 11 Use visuals

  114. @brwngrldev Jira Allow a picture to be taken of users’

    personal IDs. Each image should be cropped before upload.
  115. @brwngrldev Jira Allow a picture to be taken of users’

    personal IDs. Each image should be cropped before upload. Before After
  116. @brwngrldev Only certain users are allowed to accept payments via

    the app based on their role and country. Criteria: *FT Junior Agent in TZ and RW can accept *PT Senior Agent in TZ and RW can accept *FT Junior Agent in NG can accept *…
  117. @brwngrldev Only certain users are allowed to accept payments via

    the app based on their role and country. TZ RW NG PT Junior Agent No No No FT Junior Agent Yes Yes No PT Senior Agent Yes Yes No
  118. @brwngrldev 12 Learn about others

  119. @brwngrldev Learn

  120. @brwngrldev • Communicate Learn

  121. @brwngrldev • Communicate • Make Decisions Learn

  122. @brwngrldev • Communicate • Make Decisions • Build Trust Learn

  123. @brwngrldev relationship-based task-based Trust U.S. Nigeria

  124. @brwngrldev

  125. @brwngrldev

  126. @brwngrldev 12 Tips 1. Establish relationships 2. Have clear guidelines

    3. Use automation 4. Use templates 5. Be explicit 6. Make use of questions 7. Read before clicking send 8. POWERFUL meetings 9. Use data for objectivity 10.Simplify your language 11.Use visuals 12.Learn about others
  127. @brwngrldev

  128. @brwngrldev Talk to Me Right!