How team members communicate with each other on the daily.
...
Slack messages (and calls)
MS Teams
Jira tickets
PR comments
Emails
[remember NOT to share any password via Slack or any other medium, as it is not secure to do so. Prefer to point or be pointed towards the location where secret parameters are stored, e.g. the AWS System Manager]
App | Medium | Type of messages |
|---|
Slack  Image Modified | #CHANNEL | |
THREAD (reply to specific 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.
|
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. In this case, consider using Teams instead and record 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.
|
DMs | |
MS Teams  Image Modified | CALLS | List of MS Teams calls (@deprecated link to old pinned links) |
Jira  Image Modified | 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  Image Modified | COMMENTS ON PRs | |
Outlook  Image Modified | EMAILS | |