Swarmia gives me full visibility into the development process without micromanaging. I particularly value metrics like Flow Efficiency, Cycle Time, and Focus Summary, which help us track productivity trends and identify bottlenecks. The ability to group work by initiatives and use granular filters (such as issue type, label, or assignee) lets me tailor reports to the needs of different stakeholders. I also appreciate how Swarmia highlights things like scope creep or delivery interruptions, so I can proactively address issues with the team or client. For me, the tool is intuitive and provides just the right amount of actionable insight without overwhelming me with data. Review collected by and hosted on G2.com.

Sometimes, Swarmia classifies scope changes (like adding a small bug fix during review) as scope creep, which can be misleading. I’d love to see more flexibility in how these events are categorized or allow us to mark some changes as “minor.” Review collected by and hosted on G2.com.

I find Swarmia to be super intuitive and visually appealing with its colorful interface. I am particularly impressed with the great filters and the ease of navigation between different teams and individual contributors. This makes managing timelines across weeks and months extremely convenient. I am a huge fan of the user interface, which significantly enhances my user experience. Swarmia also provides valuable visibility both on the team level and personally. It allows me to see how the team is aligned with deadlines and goals, which is incredibly helpful for keeping track of our progress. Review collected by and hosted on G2.com.

Although I'm generally very satisfied with Swarmia's functionality, I find it can be slow when dealing with larger amounts of data. Review collected by and hosted on G2.com.

I find Swarmia incredibly valuable for gathering my team's metrics, such as work deliveries, initiatives, and developer surveys. It offers me ease of access to my team members' deliverables and provides a comprehensive view of how many pull requests they review, create, or close. This consolidated view significantly reduces the time I would otherwise spend manually collecting this information. Swarmia is very intuitive and boasts a thought-through design, making it easy to use and navigate. Logging in through Okta was seamless and required no complicated setup process. Overall, the platform facilitates efficiency and transparency in monitoring and managing team metrics. Review collected by and hosted on G2.com.

Team based time classifications could be improved. Every team might have their own method of choosing what values they deliver. Moreover, Swarmia could benefit from integrations with more tools, such as on-call shift tools. Review collected by and hosted on G2.com.

I use Swarmia for managing GitHub PRs for our team, and I appreciate its centralized location for this task. While GitHub provides a lot of tools, it can seem like it does a lot without being a master at managing PRs, whereas Swarmia excels in this area. I like being able to see all the stats about the PRs, which helps us manage expectations during retro meetings. Additionally, the initial setup of Swarmia was very easy. Review collected by and hosted on G2.com.

Nothing Review collected by and hosted on G2.com.

I like the new AI overview features, as they give great insights on how GitHub Copilot is used in my team. It helped me identify a lack of engagement with Copilot Cloud and encouraged the team to try it more. The initial setup of Swarmia was easy. Review collected by and hosted on G2.com.

I would like visibility on why some pull requests are taking a long time, like whether it's due to unclear requirements. Review collected by and hosted on G2.com.

insightfull metrics and the graphs that are helpfull Review collected by and hosted on G2.com.

not really something is dislike. Overall good experience Review collected by and hosted on G2.com.

easy to set up, insightful data presented Review collected by and hosted on G2.com.

not so much a dislike but I would like to see more ways to populate different (custom) activity types via API. some of the work of the system engineer is not visible as it's done by a ticket system. Review collected by and hosted on G2.com.

I really appreciate Swarmia for its ability to provide comprehensive insights into team collaboration and performance metrics. Over the past six months, it has become an indispensable tool to evaluate key performance indicators for the teams I manage. It's particularly useful for understanding pull request times and tracking the direction of team efforts, as well as seeing the adoption of tools like Cursor. Swarmia's focus on team-based trends rather than micromanagement aligns perfectly with my need to assess collaborative efforts and their outcomes. I am impressed by its capacity to deliver insights on a team level, rather than just individual metrics, which helps me as a CTO to report back on team contributions without the need to manually track developers’ work on various tickets. The recent release of the FTE tracking feature stands out, allowing me to retrospectively view time spent on specific tasks and understand staff efforts more effectively. Furthermore, the tool's setup was straightforward for someone familiar with GitHub, and its integration with platforms like GitHub and Jira enhances its utility. Swarmia's remarkable performance in solving a variety of problems related to team reporting and curiosity about team dynamics ensures I am confident in recommending it with a perfect score. Review collected by and hosted on G2.com.

I find the user onboarding process for developers challenging. When I invite new developers, they often do not understand what Swarmia is for and what we can accomplish with it. The initial instructions or introduction is unclear, which makes it hard for them to grasp how to proceed. The lack of a clear, initial invitation process exacerbates this issue, especially if the invitee is not part of the GitHub organization, as it prevents them from logging in. Additionally, it would be more convenient if involvement in the GitHub organization was not a requirement because I have many external contributors for different branches, which complicates managing access. Currently, I have to add all developers to the organization, which is not ideal. Review collected by and hosted on G2.com.

Swarmia has been useful both within our engineering team as well as across the wider business, giving us useful metrics with which to frame our productivity and efficiency. We utilise the Categorisation and DORA metrics extensively. It is also great when engineers are onboarding as we can monitor their fit with the rest of the engineering team. It also allows us to spot problems in our engineering workflow. Review collected by and hosted on G2.com.

Must be careful not to be too metric focused, which is a drawback of any tool like this. Categorisation is very useful, but it has taken us a while to find the right filters based on how we use Linear to get everything categorised correctly. Sometimes to find the data you need it can require a bunch of clicking around drilling down into menus. Review collected by and hosted on G2.com.

I like Swarmia's integration with Slack, which keeps our team informed on pull request reviews and issues. This helps us decrease time to review and ultimately increase our velocity. The transparency in metrics is also great as it allows us to see where we perform well and decide where we can improve as a team. Review collected by and hosted on G2.com.

A more fully-featured Issues feature could let us integrate Swarmia more into our workflow. Tighter integration with other platforms, e.g. Linear for issues tracking more incorporated into Swarmia. Review collected by and hosted on G2.com.