Best practices for Mattermost use for software development teams?

In various places I’ve seen creative uses of how channels are used as various plug-ins to support the software development process. I’m sure that people in this community have tried different setups as well, so let’s share!

1 Like

Here are some of the interesting practices I’ve seen being used at Mattermost:

  1. Create (public) channels for features in development. That is: create feature-oriented channels rather than team-oriented channels. The advantage for this is that it’s more discoverable (if you’re interested in following the development of a specific feature you can check if there’s a channel for it), also if somehow the team ownership of a feature changes, the channel will outlive. I think we don’t have great way of piping e.g. Github pull requests specific to features into such channels, but discussions and requests for code reviews can still happen in these channels.
  2. Use the agenda plugin to plan the agenda and also notes of meetings. Many teams use the agenda plugin, some then used the thread created for each agenda to take notes during the meeting — which is a great way to know what was decided on the topic for those who didn’t attend the meeting.

Those are two things that come to mind. Do you have any other best practices?

We used the GitHub project/team managing tool, and the issues feature on a dedicated repository, to track and create issues to represent various to-do’s and assign them to people from within mattermost, and provide a constant and well-organized stream of priorities and things that needed to be done and or discussed, in order to keep the project moving forward rapidly…

1 Like