Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Collaborative communication

11,445 views

Published on

Talk by Martin Alfke about collaborative communication. Talk given at Icinga Camp Berlin 2016

Published in: Technology
  • Sex in your area is here: ❤❤❤ http://bit.ly/2Q98JRS ❤❤❤
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Dating for everyone is here: ❶❶❶ http://bit.ly/2Q98JRS ❶❶❶
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Be the first to like this

Collaborative communication

  1. 1. Copyright example42 GmbH - 2016 Collaborative Communication Martin Alfke <ma@example42.com>
  2. 2. Copyright example42 GmbH - 2016 – James Fryman @jfryman “Bringing the work you are already doing ... ! ... into the conversations you are already having”
  3. 3. Copyright example42 GmbH - 2016 Communication ! ! ! ! • “You cannot not communicate.” Paul Watzlawick
  4. 4. Copyright example42 GmbH - 2016 Communication ! ! ! ! • Communication is transmission of information from a source to a receiver without loss of information
  5. 5. Copyright example42 GmbH - 2016 Communication • One can talk all day without saying anything.
  6. 6. Copyright example42 GmbH - 2016 Communication
  7. 7. Copyright example42 GmbH - 2016 Ancient Times • Pictures • Alphabet • Carved in stones • Invention of paper
  8. 8. Copyright example42 GmbH - 2016 Modern Times • Phone • SMS • EMail
  9. 9. Copyright example42 GmbH - 2016 More Modern • ICR • XMPP/Jabber • Twitter • Slack • ...
  10. 10. Copyright example42 GmbH - 2016 Collaboration • Split work load • Different expertise levels • Support and train less experienced team members • Share learning experiences
  11. 11. Copyright example42 GmbH - 2016 Collaboration • Pair Programming • 4-eyes principle • DevOps / OpsDev • NetOps / OpsNet • DevNet / NetDev
  12. 12. Copyright example42 GmbH - 2016 Communication in IT • System stati • Monitoring • Build Chain • Tickets • Communication • Email • XMPP
  13. 13. Copyright example42 GmbH - 2016 Communication in IT • need for Monitor wall • need for large screens • unsuited for remote work (unless home office)
  14. 14. Copyright example42 GmbH - 2016 Combining Communication ! ! ! ! • Dashboards (maybe rolling) • multiple sources of information
  15. 15. Copyright example42 GmbH - 2016 Communication Overlay • Why switching tools? • Why specifying content or information in multiple locations • How to ensure everybody knows the same? • What have been the tasks that were done solving the problem? (Documentation - Wiki?)
  16. 16. Copyright example42 GmbH - 2016 Aligning Communication • API-fied applications • Jira • Jenkins • Icinga2 • Puppet • ...
  17. 17. Copyright example42 GmbH - 2016 Aligning Communication ! ! • Do everything in one place • Automate everything • “Protect yourself from yourself and make your code super-secure” (J. Fryman, DevOpsDays Berlin 2014)
  18. 18. Copyright example42 GmbH - 2016 Aligning Communication • GNU approach • one tool does one thing only • second things are done with a new tool
  19. 19. Copyright example42 GmbH - 2016 Communication Simplyfied • One tool to combine everything ! ! ! !
  20. 20. Copyright example42 GmbH - 2016 Communication Simplyfied • One tool to combine everything • Monitor analysis, acknowledgement, downtime • Deployment • CfgMgmt run • Generate reports and graphs • Trigger CI
  21. 21. Copyright example42 GmbH - 2016 Communication - Old John: Hi Ben, have you seen the spike in load on backend systems? Ben: Hi John, wait, I have a look.... Ben: Yes, looks weird. I will analyse. John: Hi Ben, forget it. It was Bob running a report. John: Ben? Ben: Hi John, I restarted the server. But now we have an issue with customer sessions. Ben: Uuh. Bad.
  22. 22. Copyright example42 GmbH - 2016 Communication - New Bob: <bot> generate_report year 2014 <bot>: generating report <bot>: PROBLEM high load on backend: 8.5 John: Hi Bob, please do not run this report during peak hours. Bob: Oh. Sorry. John: <bot> icinga ack -s backend <bot>: acknowledged problems on backend <bot>: your report is ready: http://<url> <bot>: SOLVED load on backend
  23. 23. Copyright example42 GmbH - 2016 Communication Helper • Hubot - NodeJS • Lita - Ruby • Err - Python
  24. 24. Copyright example42 GmbH - 2016 ChatOps Tools • Generic helper with multiple backends (collaboration endpoints) and helpers (work scripts)
  25. 25. Copyright example42 GmbH - 2016 Demo • Lita • XMPP - Prosody • CI - Jenkins • Monitoring - Icinga2
  26. 26. Copyright example42 GmbH - 2016 Discussion • Flexibility vs. Security • Needs coding and adoption to infrastructure
  27. 27. Copyright example42 GmbH - 2016 Links • Hubot: https://hubot.github.com/ • Lita: https://www.lita.io/ • Err: http://errbot.io/
  28. 28. Copyright example42 GmbH - 2016 More Links • http://www.slideshare.net/jhand2/chat-ops-a-beginners- guide?next_slideshow=1 • http://www.slideshare.net/EvanPowell/some-chat-ops-what • http://code.oursky.com/human-and-cat-friendly-chatops/ • https://zachholman.com/talk/move-fast-break-nothing/ • http://www.slideshare.net/VictorOps/real-world-chatops • http://devops.com/2014/07/16/chatops-communicating- speed-devops/
  29. 29. Copyright example42 GmbH - 2016 Collaborative Communication Martin Alfke <ma@example42.com>

×