A good alternative to MS Teams for your Dev Ops Group
Overall Satisfaction with Slack
Slack is mainly used by our coding team and also the Dev Ops side of the house. We recently developed VoIP software as well as a program called Tadpole to help with the process for setting up a printer. It helps our Team share links to Git Repos and also provides a shareable history so that people can track changes to the software we are producing.
Pros
- Helps the team in America stay in contact with the team in India.
- Easily share links to Googe Drive, Microsoft One Drive, or Dropbox
- Conversations about coding are categorized and archived for later review.
Cons
- Some coders feel like it monopolizes their attention.
- Can create confusion if some of your team is also using Teams and they don't update Slack.
- Trouble with formatting tables that are being imported into Powerpoint presentations.
- Projects are getting completed more quickly. In some cases we can ship completed code 2 weeks faster than expected.
- We have noticed a drop in code conflicts when developers are both using the platform.
- Devs that are more accustomed to using Slack enjoy the freedom to move away from Microsoft Teams.
Teams and Slack both have Pros and Cons. We use both for communicating. Microsoft Teams is good from the prospective that you can set up Distribution Groups and Private Groups for sharing out links from One Drive and Sharepoint. The integration is built in so that all the Microsoft apps run natively with each other. Slack benefits from organizing different topics in channels that are all under one overarching project. These channels are easily created or destroyed depending on the coding issue at hand.
Do you think Slack delivers good value for the price?
Yes
Are you happy with Slack's feature set?
Yes
Did Slack live up to sales and marketing promises?
Yes
Did implementation of Slack go as expected?
Yes
Would you buy Slack again?
Yes


Comments
Please log in to join the conversation