These are the most popular teamwork tools among developers

Note: We have used commission links in this article and marked them with “*”. If an order is placed via these links, t3n.de receives a commission.

The choice of tools for team collaboration seems endless. Jetbrains carried out a survey to determine which applications are currently popular with developers.

“And how do you work together?” While the software company Jetbrains is in his Developer Ecosystem Survey actually deals more fundamentally with the development landscape, one was concerned Partial analysis of this year’s study with exactly this question. More than 47,000 people from over 100 countries took part in the survey; most of them work in the field of software development themselves. Now the company has published the results of the survey and partial analysis – in addition to tools for communication and planning, it was also about working on joint software projects.

The days of unnecessarily complicated question-and-answer dialogs via e-mail seem to be numbered, and more and more short internal agreements are being clarified via messenger. The Slack chat solution is in the ranking of the survey participants: 1st place: 47 percent of the respondents use the service, Microsoft Teams occupies 2nd place with 32 percent. Skype and WhatsApp follow far behind, each with 14 percent of users.

If you would like to see your colleagues again or have more complicated discussions, you can do so by video call. According to Jetbrains, corresponding conferences and meetings take place on three platforms: Zoom (44 percent usage) leads the way, Microsoft Teams and Google Meet are slightly behind with 33 and 29 percent respectively.

To organize video conferences and other appointments, 59 percent of those surveyed use Google Calendar, but also Microsoft Outlook (37 percent) and Microsoft Exchange (13 percent).

In order to work together, in addition to communication, you need opportunities to keep track of the project. What tasks are there, where do problems arise – and who has a solution in case of doubt? In order to make optimal use of the team’s swarm intelligence and to share knowledge, most participants use Confluence (34 percent); Google Docs (23 percent) and Google Drive (21 percent) also offer space for cheat sheets and instructions. Google Docs is also the most popular solution (39 percent) for collaborating on documents – followed by Microsoft 365 (36 percent) and Confluence (26 percent).

Those who primarily want to share documents use Google Drive (42 percent), Microsoft One Drive (23 percent) and Sharepoint (14 percent). If everything does not go smoothly in the project, problems are mainly tracked with Jira (42 percent), GitHub issues (30 percent) and LabIssues (17 percent).

In the “Tooling Stacks” category, Atlassian came out on top (22 percent), followed by GitHub (21 percent) and Google (19 percent) – a total of 39 percent of those surveyed did not use a specific stack at all. Confluence (35 percent), Jira (32 percent) and Microsoft Teams (30 percent) are mainly used for teamwork.

In addition to these more universally applicable applications, Jetbrains was of course also interested in collaboration, especially on software projects. There was a very clear favorite of the respondents: GitHub.

Both in the code review tools and in the services for checking individual versions and in the artefact / repository management – GitHub ranks first with 34, 91 and 44 percent usage. More or less closely behind in all three categories mentioned: GitLab with 29, 48 and 33 percent usage. In the area of ​​code review tools, Bitbucket ranks third with 21 percent, as does version control services with 30 percent. When it comes to tools for artefact / repository management, NPM is in third place.

Only with the CI systems did the survey results look a little different: 56 percent of the survey participants used Jenkins. GitHub Actions (45 percent) and GitLab CI (28 percent) follow closely behind. There is, however, a little twist: the survey uses a value for the rankings of the CY systems and version control services that is calculated from separate information on private and business use. If you take a look at the details and there on the purely private use, GitHub Actions slips to 1st place in the CI systems, while nothing changes in the placements for the control services.

You might be interested in that too