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

How documentation and open communication leads ...

How documentation and open communication leads to better collaboration

It's a known issue that developers often not prioritize documentation at work. Documentation and open communication are often related and critical in an open-source project environment. By the end of this talk audience members will be enlightened about how accessible documentation and open communication leads to a more productive, autonomous, and inclusive team. Also how we can apply these concepts at work having in mind open-source environment context.

Isabel Costa

August 17, 2020
Tweet

More Decks by Isabel Costa

Other Decks in Programming

Transcript

  1. Problem • Developers often overlook documentation • Lack of documentation

    in projects and teams • Cross teams miscommunication
  2. My theory • documentation leads to a more productive and

    autonomous individual contributors • accessible documentation and open communication makes for a more inclusive team
  3. Workplace • In person or remote • Fixed set of

    team members • Direct reach to colleagues • Not always transparent collaboration Open Source • Full remote • Diverse set of contributors • No direct reach to individuals • Open communication and collaboration
  4. Bus factor “(...) the number of team members who, if

    run over by a bus, would put the project in jeopardy. (...)” source: https://deviq.com/bus-factor/
  5. How can I improve • Provide clear descriptions in pull

    requests and issues • Document important decisions • Try to avoid private conversations • Responsibility of everyone in the team • Put yourself into other shoes