The Slack handbook for software development teams

Reduce organisational drag with Slack, so you can streamline work, resolve incidents and iterate faster

The average company loses more than 20% of its productive power to organisational drag.

That includes all the time that teams spend digging up requirements or coordinating on the status of designs, updates and everything else needed to bring a product to market and keep improving on it in the long run.

This handbook will show you and your team how you can use Slack to keep the development cycle agile and efficient. Work in channels, integrate apps and services that you already use and deploy various Slack features so that everyone can come together quickly, stay on the same page and spend more time focused on what matters: shipping code and improving service reliability.

Use this handbook to learn how to:

  1. Get access to key information, experts and specialists company-wide
  2. Review and deploy code from one place
  3. Track real-time performance data from multiple systems to resolve issues faster
  4. Streamline and automate workflows by connecting to services and platforms that you use regularly

‘Development teams using Slack deliver 5% more output overall, with 23% faster time to market, 27% less time needed to test and iterate, and faster identification and resolution of engineering-related bugs.’

IDC research, sponsored by SlackThe Business Value of Slack, 2017

Access the information and specialists that your team needs to ship high-quality code

More than just a place to organise conversations, public channels automatically create an archive of knowledge that’s searchable by everyone in your organisation. If you commit to doing most of your work in public channels, when someone needs more information to move forwards – such as the details of the last release – that information is readily accessible.

It’s best to reserve private channels for conversations that are sensitive or confidential and direct messages for quick back-and-forths.


‘We have what we like to call an “end-to-end delivery pipeline” that starts with source code and goes all the way through to production deployment. And now we have Slack integrated into all the key milestones in that process.’


Turn alerts into action

Manage code reviews, resolve outages and more in Slack

When you need to hash out a set of changes to a pull request or start a huddle regarding an urgent alert, Slack apps and integrations can pull notifications from a variety of systems into channels where related discussions are already happening. This way, everyone can identify potential issues and work through solutions together.

Not only does piping system alerts into public channels make it easier for managers and people from other teams to stay updated on progress, but resolving issues as a team in channels creates an automatic, time-stamped audit trail that can be useful in incident reviews. And less juggling between multiple apps and logins means fewer lags in your workday.

Integrating development tools with Slack

Connect these apps and services to your Slack workspace to manage all your build and deploy processes in one place.

Discover more in the Developer tools category of the Slack App Directory.

Keep teams aligned and processes agile

Working together in Slack

Now that you’ve seen how channels, apps and integrations connect you with the people and tools that are important to your team, let’s take a look at how you can bring more of your daily operations into Slack. When teammates work together in channels, they can support each other in delivering their highest-quality work and spotting potential issues before they arise.

Create and share code using snippets

Share code, configuration files and log files with snippets, which work with a variety of programming languages. Team members can download them, view the raw file and leave comments.

Spare yourselves a meeting: hold huddles in Slack

Find out who’s working on what, the status of a project and any stumbling blocks by moving huddle meetings into team channels in Slack, where they can be searched for later on. Or why not let an app facilitate? Teamline and Standuply are both popular options.

Track issues and spot patterns with a triage channel (and emoji)

To maintain quality and stop worrisome trends in their tracks, create dedicated triage channels (such as #triage-iosapp) where people from across the organisation can report bugs, issues and irregularities. We recommend assigning a team member as triage captain for the day to help field questions and direct top-priority issues to the right teams.

Sending signals with emoji.

Emoji add a lot of helpful context to messages in Slack. In the case of triage channels, they can also serve as a diagnostic tool, helping you to track trends and see patterns in behaviour over time.

Build with your team, for your team

Creating internal integrations

While there are many apps available to connect to your workspace, there may be cases where you need to tailor a workflow to your team’s needs. And that might mean bringing even more of your tools and data into Slack. Internal integrations help you to do just that.

Use internal integrations to combine data from multiple resources into one message, so you can manage DevOps, deployments, CI and incidents and even approve wireframes, without ever leaving Slack. Here are some other handy applications.

Use case: Shopify’s super Slack apps

The e-commerce platform Shopify operates more than 500,000 online shops. To keep the virtual doors of all these businesses open, the company has created more than 180 internal integrations for Slack. The most popular, Spy, allows Shopify to run hundreds of custom commands, such as querying information about the most active shops, traffic volumes and checkouts, inspecting and operating servers across data centres and creating new GitHub repositories, without ever leaving Slack.

Ready to explore integrations? 

Start building at and make sure to take a look at the app blueprints for detailed instructions, code samples and helpful flowcharts.

What’s next?

There’s plenty to digest in this handbook, so here are a few things that your team can do at the outset to streamline your workflows, speed up your processes and make information more accessible across teams.


  • Do a little channel clean-up: maintaining good channel hygiene is essential for keeping communication between teams and departments crystal clear. Make sure that you periodically audit your channel list, archiving ones that are no longer relevant or useful. Take a look at these tips for reducing noise in Slack.
  • Rethink your channel names: is there a consistent naming convention across all your channels? Are they labelled in a way that makes their purpose obvious? Take some time to rename channels so that they’re easy to find and follow. Learn more about channel naming best practices.
  • Give some apps a whirl: connect a few key services that you use often (such as your go-to bug-tracking tool) to your team’s workspace and try sharing and updating data directly in Slack. Explore marketing apps for Slack.

For detailed tips and how-tos on organising channels, working with apps and more, visit our Help Centre. Or, if you prefer to talk to a human, get in touch any time via or find us on Twitter at @slackhq, and we’ll be happy to help.


  1. Michael Mankins and Eric Garton, Bain & Company, Time, Talent, Energy, 7th March 2017.

Was this resource useful?


Nice one!

Thanks a lot for your feedback!

Got it!

Thanks for your feedback.

Whoops! We’re having some problems. Please try again later.