- Asana/Jira/Trello etc.: usually within this type of software, communication is conducted based on a task. It can take the form of information requests, comments/suggestions and so on. This is a very organised way of keeping task/story information in one place so that it is easily accessible by all involved.
- Slack: usually within Slack you will find that Upstack has an internal channel for each project and there is an additional client channel. The internal channel serves the purpose of team & organisation wide communications, so a developer might say: ‘tester please go ahead and have a look at the login function, let me know what you find’. On the client channel, it is normal to expect all sorts of communication, from announcements to discussions on designs, questions and answers and so on.
- Daily Stand-ups: although discussed previously, it is important to emphasize that daily stand-ups are core functions, that make the development process work smoothly. For the purpose of this heading we will remind the developer that these are mandatory (unless emergencies or personal issues occur). If for any reason, a team member cannot take part in a daily meeting, it is required that they present a written update (on the client slack channel) that is composed in the same form as the update that would have been provided during the meeting.
If you have any additional questions please do not hesitate to contact your Project Coordinator: Robert Dragne - either on Slack or through an email: firstname.lastname@example.org