Open WorkBench vs. Slack

Slack is ideal for Scrum and agile teams that need continuous communication during sprint planning, daily stand-ups, backlog refinement, testing, and retrospectives. Slack is well-suited for maintaining team knowledge through searchable conversations and dedicated channels, where experienced team members help onboard new QA analysts.

• Huddles Run smoothly without any interferences.
• Smooth individual calls quick and easy without any interruptions.
• seamless notifications across multiple devices
• The ability to easily tag a team member to urgently attend to a specific escalation.
• Slack being user friendly and able to integrate easily with other platforms and apps.
• How to easily open up different channels for different escalations and needs.
• a safe direct messaging option.

Incentivized

• Would love a better integration with GitHub. For example, notifications when your PR is updated, when review is requested, @-mention in comments, etc.
• Improved "Later" tab, for example the ability to create to-do lists or making the "Later" tab into a more powerful to-do list (annotate items with notes)
• More powerful integrations, e.g. Google Calendar could render a calendar view within Slack, rather than sending the daily schedule

Incentivized

Slack sitll lacks in functionality. It's better than Skype for Business in many ways, but it is still another chat/message board app. It has limits in free version and paid versions. Also Windows app has errors that bother me, for example, I see number on one of my team's icons. It suggests that one of channels has unread messages; I check all channels - no unread messages, but that "1" still appears

Incentivized

My rating was 7. Its intuitive interface and user-friendly features like channels, threads, and integrations make it excellent for team communication and onboarding. However, its usability is held back by the resource-intensive desktop app and cluttered feeling in large workspaces. The mobile app's performance and unreliable notifications have also been noted as weaknesses.

Yes, the app works 24/7. I don't even recall having any period that we could not use since the implementation. Even the maintenance periods are barely noticeable and our work is not impacted by it when it happens.

Incentivized

Slack is a soft app, we don't have many issues with it. I recall one or two people complaining about something during our usage period, but I didn't have a bad experience. When the app is slow, usually the problem is with my computer or my internet. The app works just fine.

Incentivized

Whenever I've had to troubleshoot an issue with Slack (which, to be honest, has not happened very often), their online documentation has been easy to locate, easy to understand, and effective in resolving my issue. Slack's ever-growing popularity also means that there's a large community of practice out there that can be depended upon.

Incentivized

I was not part of the implementation team, but I recall being 100% happy and excited to learn and use a new tool. I'm still am to be honest.

Incentivized

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.

Incentivized

• Our leadership team uses Slack communication to directly reach employees. This allows us to be aligned with the company objectives.
• Communication amongst the team stays effective and at one place. This improves the alignment.
• Slack has proven to be effective in managing site incidents. Allows us to dynamically pull resources as needed and get a fix in place.