Swarmia Reviews & Product Details

Our company is implementing DORA metrics, and there is a lot to consider when making this change. Swarmia does a great job of helping from beginning to end. Their software easily connects to Jira and Github, ensuring we have all the correct data. They also have easy-to-understand charts and notifications, allowing me to review team metrics and suggest changes to the team at daily standups.

For those who have never used DORA metrics in any capacity, their support team members can help with that, too! They offer a lot of helpful documents that show me not only how to use their platform, but also how to explain the purpose of it to my team.

TLDR: you need Swarmia. Review collected by and hosted on G2.com.

We have yet to fully utilize the software cap portion of their platform, but every day it's getting better and better. Once it's finished I think we're going to love it, too. Review collected by and hosted on G2.com.

It gives you a very good overview of the work and the whole workflow. I really enioy being able to see the ongoing team Pull requests and being able to jump straight to the ones that need review. I also like the Slack notifications, which give you much more information the GitHub integration.

I also like that it guides teams to improve their work management and guides them towards better processes. I think this is a byproduct of using Swarmia, not an explicit part of it. Review collected by and hosted on G2.com.

As an engineer, I feel like Swarmia can give "Big Brother vibes"; while it depends on each organization on how to use it, I feel like it can be misused to micromanage or monitorize people and teams. And if work is not properly organized or if there's work that's not visible in Swarmia, it can create bias towards some people. Review collected by and hosted on G2.com.

The modern user interface with nice visualization allows to see data in various ways.

Great summary on yearly recap and makes you want to contribute even more when seeing own contributions in various ways. Seeing missed things on 'working agreements' section so it is easier to remedy those. Great pricing. Had no idea it was Finnish company that ran Swarmia until had this review request, but it is a great plus. Review collected by and hosted on G2.com.

Nothing comes to mind that works bad or is buggy so if I'd have to say something then maybe lack of dark mode for the user interface. Review collected by and hosted on G2.com.

One of the things I really like about Swarmia is its generous free tier. It gives teams like ours access to a bunch of useful productivity tools without any upfront cost, which made it super easy to get started and see how helpful it could be. Another thing I love is the Slack integration. The Swarmia bot sends out daily “Standup” messages, letting us know which PRs and Jira tickets are still in progress. It’s great because we get real-time updates without needing extra meetings or manual check-ins.

The “Work Agreements” feature has been a big help too. We’ve set ours to review PRs within 2 days and merge them within 3, and Swarmia sends us an alert if we’re falling behind. It keeps us on track without much effort. I also like the breakdown of everyone’s progress—how many PRs they’ve reviewed, created, merged, etc. It’s a nice way to see how the whole team is doing and keep everyone accountable and motivated. Review collected by and hosted on G2.com.

Integrating Swarmia with Xcode Cloud without the need for custom API work would be a significant enhancement. This integration would provide valuable insights into flaky tests, CI failure rates, average CI times, and more. Having this data readily available would help us diagnose issues faster and optimize our CI/CD pipeline. Review collected by and hosted on G2.com.

Swarmia is very easy to set up and integrate with the tools we already use. The daily digest is great for helping the team get notified early of metrics that are trending the wrong way. The notifications and slack integration have been a really great tool in combining the best of both worlds when delivering important information from our git and change management tools. Review collected by and hosted on G2.com.

Swarmia has been great at delivering raw data. One thing I'd like to see them add is more opinionated aggregates. Things like the quality and engagment of PR reviews vs raw PR data. Review collected by and hosted on G2.com.

Way how clean graphs are built. Clean design, good on-air updates with the filters. Good switch between some data, but with some flaws. I'll put more in the second window, as a challenge. Review collected by and hosted on G2.com.

What Im missing:

1. When I work more with the analytics or design team - I have specific issue types, which sometimes I want to compare all together, f.e. stories + tasks + bugs, if we have specific mix, I cant do that, or I do not know how to do that together, without switching on left menu tabs.

2. When I work with custom field data(f.e. Story points) - I try to check what differences in cycle time on differently estimated stories and its each time ask me to setup this through selection of advanced option of custom field. Please consider adding a save option(temporary, without going so deep as with labels f.e.) so I can have session of data compared. Review collected by and hosted on G2.com.

It is easy to use. After having the onboarding session, I found it easy to get myself onboarded and get used to. Review collected by and hosted on G2.com.

Some screens does not have a loading spinner. Then it becomes difficult to understand what is happening. Review collected by and hosted on G2.com.

- It offers interesting data on team activities like pull request review times and commit frequencies.

- It offers greater visibility into the team’s coding and review activities, which can aid in process optimization.

- It integrates easily with other tools like Linear and Github

- The UI is clean and it's easy to use

- It's easy to try it out and slowly implement more of it's features into your teams workflow over time Review collected by and hosted on G2.com.

- The usefulness of the metrics depends largely on how they are interpreted and applied by the team. Software productivity is hard to measure. Swarmia tries to address this by providing an "Insights" section, which points you in the right direction towards making proper adjustments.

- The tool can be useful for managers to monitor team activities and workload distribution.

- The value of code written is not in the number of lines or number of commits made. This is the part that Swarmia doesn't capture. Review collected by and hosted on G2.com.

Swarmia has been incredibly useful in providing clear insights into where our development teams are focusing their efforts. The ability to redirect our teams based on these insights ensures that we stay on the right path. I particularly appreciate the performance metrics, which give a clear picture of how well my team is performing. The recent addition of the beta survey feature has been a game-changer, allowing us to measure the cultural aspects of our work without having to develop a tool from scratch. Review collected by and hosted on G2.com.

While Swarmia excels in performance metrics and focus tracking, it initially lacked tools to measure the cultural aspects of team. The beta survey feature has addressed this to some extent, but there is still room for improvement. I would love to see built-in analysis tools for survey responses. Currently, I download the responses as an Excel file and create a dashboard in Google Data Studio to measure these aspects. Being able to analyze these metrics directly within Swarmia would be fantastic. Review collected by and hosted on G2.com.

Easy to see general overall activities on PRs. I find PR duration for in-progress time and review time helpful, this helps us to find bottleneck in reviews or identify if the scope of the task was too big. Review collected by and hosted on G2.com.

In progress time of calculation is not correct for our engineering team workflow. We create draft PR as soon as we start the task, we expect in progress time from the draft creation to PR marked not draft. However, Swarmia somehow picks up time from commit that was made way earlier and use that time instead of draft creation time. This end up capturing in progress time wrongly. Imagine a branch `feature1` was created from `master` and a first PR created from `feature1` branch. Then `feature2` branch was created from `feature2` because well some implementations have dependencies. Now a second PR created from `feature2` contains commit from `feature1` branch, which on Swarmia captures the easliest commit from `feature1` as start of the in-progress time. For us, this is wrong. The correct in-progress time for the second PR for us is from the time second PR draft is made. Review collected by and hosted on G2.com.