Internal Communication

 Overview

Communication is one of the most important parts of any development process. It is the process that requires incredible soft skills in order to do the job correctly. In development there are certain rituals and best practices that are required. Such will be listed below.

 Communication Rituals


Here will be listed all the required Internal Rituals in regards to communication

Daily Stand Up Meetings

• All projects must have stand up meetings on a daily basis where all developers must be.

• The Daily meeting for each project must take not more than 15 minutes

• All Stand up Meetings must be scheduled in the Calendar with all of the participants on a daily basis

• All the stand up meetings must be noted in confluence with the Daily Standup meeting template

  

  Only titles of the table should be changed:
  Priorities – What was done?
  Progress – What is planned to be done?
  Problems – Blockers

• The notes must be taken in every confluence space of the project on a daily basis

• If you see that a lot of your developers are one multiple projects, you can combine the standup, but notes are to be added to each project separately.

• Communication must be logged separately in a communication task for each developer separately.

• Use Zoom in order to record a meeting if you feel it is required

• Make sure that everything is being told straight to the point, in order to “not waste time on water”

• If somebody does not have an opportunity to join, the developer must write down the status in the slack channel, which will be added by the Project Manager to the confluence page

• Each project, even if a small one, should have a channel in slack with all the developers added in order for quick communication

• There will be 1:1 on a weekly basis with PMO