4 Best Practices for Software Development with Mattermost an agenda, or whatever use your team comes up with. The key thing is that they are col - laborative and open to the team so members can, for example, pick up a task to work on, and team leads can monitor the progress of the project. Boards directly support other best practices such as standup meetings, sprint planning, setting milestones, scrum ceremonies , retrospectives and more. For example, here’s a simple stand-up meeting board with columns for `To Discuss`, `Revis - it Later`, and `Done`. Participants queue items to discuss throughout the week, which the team can easily go through at the meeting, revisiting topics as needed. Use version control and project tracking Version control systems are a critical software development best practice. Git is the de facto standard for tracking and managing code changes especially for a distributed team . The key here is that changes are tracked in small increments, and changes can be rolled back to a previous version if something goes wrong. Many developers can be working safely and simultaneously, and anyone can look into the project history to clearly view what happened. As a developer working with a project stored on say, GitHub, you may get a lot of notifica - tions from GitHub for comments on issues, code review requests, pull requests, and more. Whether those notifications appear in a web browser, via email, or somewhere else, it’s one more place you need to check for messag - es. Mattermost offers a direct integration with GitHub (and GitLab) so that your notifications appear directly in the Matter - most App, alongside your conversations in Channels. You can also interact with your GitHub account using slash commands for the integrated bot to subscribe a channel to a GitHub feed and more, so that everyone in the channel stays up to date.