Intrateam communication

SLACK #CHANNEL

• Generic messages meant to be read by all those who’re part of the channel.

• Messages that may be aimed at specific members but that could benefit from being exposed to a wider audience.

SLACK THREAD (response to one particular message)

• Response to a specific message that feels like it’d spam the channel if it was posted on it. When there’s an opportunity to start a thread that pertains a topic that is focused on some defined details it’s best to take it.

• Any message that feels like it’d be only nuisance to other people in the channel that most likely won’t need to get involved with that issue.

SLACK CALLS

• Anything that requires people talking vocally and probably screen-sharing (charts, roadmaps, slides, code etc.).

• If it’s a discussion over a subject, it’s good practice to jot down a few notes and post them in the same channel shortly afterwards to let the wider team know what was said/discussed/decided on the call.

• A call in a channel is preferred to a call between single individuals if there’s a chance anyone wandering into the call might provide helpful insight.

• Ceremonies (standup, retro etc.) should not happen on Slack, but on MS Teams.

SLACK DMs

• Anything that feels like it’d be of no interest to anyone in the channels.

MS TEAMS CALLS

• List of MS Teams calls

• Planning

• Standup

• Ticket refinement sessions

• Team sharings

• Sprint Review

• Retro

• Estimating Session

Jira TICKET COMMENTS

• Anything that explores the actual implementation of the ticket’s goal

• Anything that would enrich the story described in the ticket and that feels valuable to immortalize for future reference (rather than having to browse through Slack messages from months back)

Github COMMENTS ON PRs

• Anything that needs to be addressed in a PR that is being peer reviewed.

EMAILS

• Usually for formal correspondence