To me or seems that the author is more frustrated with how his team communicates during a sprint than the tool being used.
If you need to discuss something in thorough detail in a sprint, which is on the sprint backlog, it is done during refinement.
If a discussion is about a work item/pbi/user story it is discussed not in Slack or Teams, but under the item's discussion board. Jira, base amp and azure DevOps all support this.
The symptoms of poor communication or following a proces cannot be deslt with be changing from Slack to email.
People needs to be educated it seems as where communication must go.
Emails are not for work items under a sprint. Imo. Neither is Slack. You don't discuss wotk items in a chat, you do that in it's appropiate platform where the item livets.
Slack is not email. Should not be used as such. Slack is for "hey, where is that vacation spreadsheet" and not "should this feature be with bootstrap or vanilla HTML?"
The latter is work. It is discussed where work lives. Work does not live in Slack.
If you need to discuss something in thorough detail in a sprint, which is on the sprint backlog, it is done during refinement.
If a discussion is about a work item/pbi/user story it is discussed not in Slack or Teams, but under the item's discussion board. Jira, base amp and azure DevOps all support this.
The symptoms of poor communication or following a proces cannot be deslt with be changing from Slack to email.
People needs to be educated it seems as where communication must go.
Emails are not for work items under a sprint. Imo. Neither is Slack. You don't discuss wotk items in a chat, you do that in it's appropiate platform where the item livets.
Slack is not email. Should not be used as such. Slack is for "hey, where is that vacation spreadsheet" and not "should this feature be with bootstrap or vanilla HTML?"
The latter is work. It is discussed where work lives. Work does not live in Slack.
Good luck