Celebrate when you get a larger project completed with a new team notification. Get a summary of the key metrics like scope creep, active days, longest-running tasks, and more — right in Slack.
In Swarmia, when teams agree on an improvement area, they adopt a working agreement. It’s the starting point to measure where the team is at right now and to set a goal for the future.
But setting a goal is no guarantee that change will follow. Things tend to get lost and forgotten, and what’s brought up in retrospectives is not always taken forward.
80% of teams using Swarmia get our daily digest that provides a feedback loop for their continuous improvement goals. It contains a daily status update on all working agreements and a summary of actions required from the team. Now you can choose what data to include in the digest!
The best teams know where their time is spent and balance efficiently between the most impactful work and housekeeping. It ensures they can reach the high-impact business objectives and solve the right problems in the short term, without compromising the capability to do so over the long term.
Here are some common anti-patterns to observe when it comes to allocating time:
Swarmia’s new investment distribution view gives transparency to the different areas of work teams focus on to help you achieve a balance in how the time is spent.
Use it to see your time allocation by area, and drill down into individual projects to investigate further.
Security is an integral part of Swarmia, and since the inception of the product, we’ve been conducting regular security reviews twice a year. In July 2021, we completed our latest security audit and training based on OWASP ASVS 4.0 controls.
Our goal is to bring transparency and insight into the entire product development process and empower software teams to own their ways of working. When we introduce high-level metrics like cycle time of pull requests and issues, our primary focus is on data quality (see more in our help center). We break high-level metrics into contributing factors allowing teams to investigate their development workflow in greater detail — ultimately, it's all about making insights clear and actionable.
Swarmia’s holistic approach has gotten even more complete with the addition of deployment insights. Now you can see deployment frequency, average deploy time, and deploy success rate in Swarmia.
We use GitHub’s check runs to analyze deployment data. Enable deployment insights by selecting relevant check runs in repository settings in Swarmia.
We’ve improved the performance of all charts and tables. Now it’s easy to load up to a year’s worth of data on a team's performance — helping to spot trends and outliers that aren’t as clear on shorter timeframes.
You can now see the exact time intervals included in cycle time calculations for all issues: just hover over the time an issue was in progress anywhere in the app.
If an issue was in progress more than once (it happens if it was moved to in progress by accident, or returned to backlog half-done), only relevant time intervals are counted towards the cycle time.
Measuring and limiting work in progress is at the core of continuous improvement. When a team works on too many things at once, things move slower, affecting the team's ability to deliver value. Introducing work in progress limits helps increase flow, boost focus, and create the slack necessary to plan new work and improve ways of working.
Work in progress can be measured on a few different levels. At Swarmia we visualize what's in progress both for code - pull requests - as well as for issues in progress. Swarmia's Insights show the relationship between work in progress and cycle time, helping teams to arrive at an optimal WIP target and set up a working agreement to spot early signals of WIP increasing.
With the latest update, it's possible to select multiple teams in pull request insights to see how individual teams' WIP and cycle time trends compare to the rest of the organization. In addition, it aims to show if the observed trends are team-specific or reflect the general direction of the organization as a whole.
To access cross-team insights, select more than one team in the dropdown on top. As of now, it's available for PR insights only, but we’re planning to bring the same functionality to issues next.
Lately, we’ve been busy improving our pull request insights to help teams explore and understand the raw data behind cycle time, review time, and other metrics. Now we’re bringing the same improvements to issue insights.
Use them to get an overview of cycle times, scope size, and scope creep for all ongoing and completed issues. We've found that even in best-performing teams scope creep is not uncommon, and some variation in scope is totally normal. Yet it's important to look into what makes scope grow (tasks added while you're already working on a feature) to improve the quality of the planning. We've also added a rolling average trendline to all charts to help you follow work in progress and cycle time trends over time.
Next, we’re working on new high-level insights that show trends across all teams in an organization. Let us know if you’re interested in getting early access to try them out.
Remember that time when a small and straightforward project ended up taking weeks or even months to complete? We all have been there. Today we’re excited to introduce new tools to help you diagnose flow issues, recognize scope creep signals early on, and improve planning accuracy.
👉 Select an issue in Work Log to see a burn up chart with all tasks added and completed over its lifetime. New tasks added while an issue is in progress count towards estimated scope creep.
Swarmia’s notifications are designed to help you focus, save time, and enable powerful workflows — like linking pull requests to issues — right in Slack. We care about keeping the noise level to a minimum: if you get a notification from Swarmia, it means an action is required from you.
With the latest update, you have even more granular control over notifications you get from Swarmia. Now you can choose what comments and PR-related updates you want to be notified about.
Getting high-quality data about your pull request pipeline is the first step to a better understanding of process changes that improve velocity and quality. Our new pull request insights are here to help. See some key highlights below.
➡️ Cycle time average graph (on the right) shows how long it generally takes you to close pull requests, and how the situation develops over time. If you close pull requests timely, it trends down. Pull requests left open for several days result in an upwards trend. Aiming to close all pull requests in under a week (or 1–2 days on average) is a good starting point for uninterrupted delivery.
⬅️ Pull requests in progress graph (on the left) gives a clue into how your ability to close pull requests is affected by the number of pull requests worked on at once by the team. Working on too many pull requests at once can result in longer delivery times, and we recommend adding a work in progress limit (e.g. up to 7 pull requests open at once) to make sure pull requests piling up don't slow down the team.
➡️ Cycle time distribution chart (on the right) shows what portion of pull requests takes longer than expected to complete, and individual pull requests are shown in the scatter plot on the left. Pull requests far above the rolling average line need special attention — it’s the code that’s been waiting for the longest to be delivered.
Filter the pull request table by status, repository, or author (by clicking the filter icon in the table header) to identify problematic pull requests. Filters apply to the table as well as the charts above.
Review time is another important contributing factor to cycle time. Sorting the table by review time helps to identify pull requests that have spent the longest in review — or have been merged without review at all. The number of pull requests merged without review is reflected in the review rate above the charts.
Tasks completed with no coding activity are now shown at the bottom ofWork Log making it easier to see where the engineering team’s focus has been week to week.
Old open pull requests can make pull request cycle time metrics difficult to interpret. Our new Pull Request Archive provides you the option to hide old and stale pull requests in Swarmia. This is especially useful for you to start focusing on improving ways of working when adopting Swarmia without letting the burden of the past get in your way.
If your team has pull requests with no activity since the last 30 days Swarmia prompts you the option to archive them on the Pull Request view.
Archived pull requests are excluded from all metrics in Swarmia and Slack daily digest. After archiving, you can still browse them on the Pull Request view.
Your colleagues can now sign up to Swarmia directly from our website. Based on the new user's GitHub account details, we can identify and link the user to your organization in Swarmia. In addition to providing a self-signup option, you'll still have the option to share an invite link (available on the app front page) with your colleagues.
Code review helps ensure code quality, and share knowledge within the team. Yet even among teams performing code reviews regularly, pushing unreviewed code to master is not uncommon. Our new working agreement helps track all commits merged to your main branch without review, and start a conversation within the team if it becomes an issue.
See how your team is doing under Explore → We don’t push code directly to main branch. Connect Swarmia’s Slack digest to get a daily summary of all unreviewed code pushed to production.
Now you can choose GitHub teams to show in Swarmia, and hide teams that do not represent actual development teams in your organisation: for example, if you use teams for access control. We’ve hidden some of these teams automatically based on Swarmia usage. 👉 See them all here.
A software team’s velocity is a combination of many factors. Looking into pull request pipeline by stage is a great starting point to identify bottlenecks and get pull requests through faster. With the new cycle time breakdown it is easy to see whether review, merge, or WIP time takes longer than expected.
You can also use Swarmia’s filters to look at cycle time and throughput metrics for bot-created, cross-team, and other PRs separately.
The chart below cycle time shows how your pull request queue trends over time. When multiple pull requests are left open for long, it trends up. When pull requests are merged timely, it trends down. Many teams will notice that Christmas bump on longer timeframes where cycle time increases during holiday time 🎅.
Previously, pull request age was calculated from the moment a pull request was created, and earlier commits would not get reflected in cycle time insights. Including time since the first commit allows better comparison between pull requests and makes pull request insights more accurate.
Our goal at Swarmia is to help teams to get a holistic picture of where their time goes, improve flow and make better planning decisions.
Using Work Log is an excellent way to keep track of day-to-day work and spot patterns like siloing, reactive works, and multi-tasking early on.
With the new high-level Work Log, it’s easy to zoom out and see everything you worked on over the past year. Use it to diagnose flow interruptions, spot never-ending projects, and prepare for team retrospectives.
It’s also a great tool to see just how much you got done and celebrate your progress with the team 🥳.
Knowing where the time goes starts with bringing together the data from where work happens. Linking pull requests to issues is a great starting point. It enables better Work Log insights and helps the team to have more informed conversations about how to organize the work.
Sometimes a PR in review might get a lot of comments, but they`'`re all just observations. Now you can immediately tell from the Slack notification if your PR is good to go or has anything left to improve. Configure personal notifications here.
In a well-functioning team, PR reviews move forward fast, and resolving issues highlighted in review is a priority. Now, as you reply to a PR review thread, you will get notified about all new comments until the thread is resolved.
Following up on the latest updates to the PR overview helping you manage your team’s PR inbox, we’ve added a new section for bot-created PRs.
For all bot users in your GitHub organization, you should be able to see their contributions in Swarmia already. You can also assign bots manually in contributor settings.
Swarmia continues to build tools that surface the otherwise invisible work in software teams and help you get a clear picture of your pull requests inbox. Now we’re adding new essential filters providing an at-a-glance overview of all pull requests in both personal and team context:
Soon, bot-created pull requests are getting a new home too. Contact us for more details.
Working agreements are a powerful tool teams use to adopt and keep track of better working habits. Every once in a while, an exception to the rule occurs, and Swarmia already helps you to review those old PRs or a never-ending story that escaped your agreements in the recent past.
Now it’s even easier to prevent future exceptions as you can keep track of all that escapes your agreements ⏰ right now. Aim for inbox zero, and review your agreements with the team frequently to make sure the new habits stick.
Working agreements work best with the daily digest. Once an agreement is adopted, it appears in the digest with a link to all active exceptions.
Keeping pull requests inbox in order is the foundation of a healthy software team. With the updated pull requests overview, it's easy to see all work in progress at a glance:
This update is part of a series that makes Swarmia your go-to place for everything PR-related. Coming next:
Share your feedback and suggestions at firstname.lastname@example.org, or using the chat button anywhere in the app.
Making a long-lasting improvement to working habits is impossible without a strong feedback loop. With that in mind, we've built our Daily Digest — a Slack update aligned with your daily stand-up meeting that provides a brief summary of pull requests, issues, and working agreements that need your team's attention,while keeping the noise level to a minimum.
Now it's even more actionable and concise:
Set up your digest in Settings. Make sure to select your team's main Slack channel for better visibility. We're eager to hear your feedback, feel free to send us a message using the chat bubble in the bottom right corner of the app.
See all completed, in progress, and to-do subtasks in a progress bar below each issue in the Worklog. Now it easier to stay up to date with the issue scope, and status of subtasks in your projects.
We continue adding improvements to Work Log that give you a broader context to issue activity. Now we show everyone who has worked on an issue over its lifetime, with recent contributors highlighted.
Swarmia’s Working Agreements have already been helping teams when it comes to managing work in progress and cycle time. Many teams have found them especially useful to manage issue workload, and to get notified when issues are taking too long. However, a limitation so far has been the ability to only create working agreements about one issue type.
Managing the amount of work in progress is one of the most effective ways for a team to maintain focus and deliver tasks quickly. Imposing work-in-progress limits for Stories has been an important tool for teams struggling with too much work, but this has precluded setting similar limits for Epics, Tasks, or Bugs. At the same time, most teams have an idea about how long different tasks should take. For example, Stories should usually be completed within a week or two, whereas Tasks can be significantly shorter, and Epics significantly longer.
Swarmia now allows teams to adopt multiple copies of issue related Working Agreements. For example, teams can impose work-in-progress limits for both Stories and Epics, and also manage the cycle times of both issue types. If you’ve already adopted Working Agreements about the number of Stories open at once, or targets for closing Stories, navigate to the Explore tab in Working Agreements, select either working agreement, create a new configuration, and click Adopt another.
In this case, a team that has already agreed to have a maximum of three Stories open at once can adopt another Working Agreement, this time limiting the number of Epics open at once to one. Adopting multiple, identical Working Agreements is of course not supported or useful. Adding multiple copies of Pull Request related Working Agreements is also not supported.
Our new Insights about Pull Request review times have been useful for teams with delays in this crucial step. Most teams are mostly alright in terms of review times, with significant outliers causing problems. To help teams understand the magnitude of issues with Pull Request review, we’ve added a new histogram that shows the distribution of review times, and we also now spell out the median review times separately for all issues, issues reviewed by the team itself, and issues reviewed by other teams.
Swarmia’s Insights already help you keep track of your Pull Request and Issue cycle times, and we also let you set targets for Pull Request cycle time with a Working Agreement. This week, we’re releasing new features that help you drill down to the Pull Request review time, and to set targets for Issue cycle times.
Making sure that code is reviewed without delay is one of the most important things you can do to improve team dynamics and throughput. Our new Insight and Working Agreement lets teams specifically improve the time it takes to review code. The time to review code is a leading indicator of the Pull Request's total cycle time, and counting working days only lets the team set aggressive goals for this crucial step.
A new scatterplot in Pull Request Flow Insights shows how long it takes to provide a review after one is requested. To help organizations dealing with delays caused by cross-team dependencies, reviews provided by other teams are highlighted in a different color.
The corresponding Working Agreement helps your team step up your Pull Request review game by setting a target for how many working days Pull Requests wait for review.
As with other Working Agreements, details about exceptions help your team troubleshoot your process in retrospective meetings, and instant feedback in the daily Slack digest helps you address issues with Pull Requests reviews as they occur.
You can read more about why and how to review code faster in our Support Article.
Most teams have a rough idea of how long it should take to finish an Epic, Story or Task, but it’s common for progress on Issues to stall for a multitude of reasons. Our new Working Agreement helps teams manage cycle time by setting targets in calendar days and highlighting exceptions.
In addition to the Working Agreement page and the daily Slack digest, issues that are taking too long are highlighted in Work Log to help teams analyze exceptions in context.
Linking Pull Requests to issues from your issue tracker is the best way to keep tabs on your team’s focus and flow using Work Log. But when teams self-organize around caring for a codebase, it’s just natural that not all Pull Requests can be linked to an issue.
It’s great when teams take ownership of their code and deal with small bugs, chores and improvements right away, but it’s still useful to understand where the team’s efforts are spent. This week we’re introducing a powerful new feature to categorize Pull Requests without linking them to issues.
Previously, all unlinked Pull Requests were plotted on the Uncategorized row in Work Log, with no quick way to identify what kind of work it was. The new Pull Request Categories feature lets you assign unlinked Pull Requests to one of four categories: Bug, Improvement, Chore, or Refactoring.
Unlinked Pull Requests can be assigned to a category by selecting it in the familiar dropdown menu in the Pull Request dashboard:
As usual, we notify you on Slack when merging an unlinked Pull Request. Now you have the option to click a button labeled It’s something else and select a category:
As a result, Work Log shows a much more accurate view of where the team spends its focus. Unlinked Pull Requests assigned to the Bug category are plotted right on the Bugs swimlane, and the newly renamed Unplanned swimlane shows a breakdown of the week’s unlinked Pull Requests by category.
Work Log already helps you visualize where your team’s focus is spent on a weekly basis and to identify common patterns having to do with team dynamics and focus. The all-new Issue Insights feature lets you drill down deeper on an individual Epic, Story, Task or Bug to find out how your team organizes around issues, and what you could do to increase focus and accelerate delivery.
Navigate to Work Log and click on an issue. This opens the Issue Insights popup that shows a number of key facts.
Open days is the number of calendar days since the first linked GitHub activity, or since the issue was marked In Progress. Active days is the total number of days with activity linked to the issue. Efficiency is the ratio of Active days to business days.
The calendar shows the intensity of activity linked to the issue per day: the darker the shade of blue, the more activity on that day. To take a closer look at what your team was working on in a given week, clicking a week in the calendar takes you to that week in Work Log.
Ideally, we want to see long streaks of dark blue in the calendar. Teams that put in big chunks of focused work tend to finish fast, even if efficiency is under 100% — short interruptions like vacation days and urgent bugs are hard to avoid completely.
Often the reality is that team focus is stretched too thin. Even with 100% efficiency, progress can be slower than necessary if contributors are working alone or there are many concurrent topics competing for the team’s attention. This is evident in the issue insights calendar when progress is steady, but most days are a lighter shade of blue.
Unfortunately, it’s all too common for teams to be inundated with work in progress and constant interruptions. Slow progress with lots of waiting is clearly visible in the issue insights calendar with long periods of grey inactivity interspersed by light-blue days here and there.
How is your team doing? Head over to Work Log and click on some issues to find out!
To get the full benefits of Swarmia’s Work Log and the new Issue Insights, it’s important to get into the habit of linking Pull Requests to Jira issues. Swarmia now posts a comment in each linked Pull Request to confirm that it’s been linked, as well as to help you quickly check the respective Jira issue for scope, designs and other context by following the link in the comment.
In addition to Jira, most Swarmia features are available now for Linearusers as well. Link Pull Requests, view Work Log by Linear project or issue, and view Insights about Linear projects and issues. Let us know if you’re using Linear and would like to look beyond Pull Requests with Swarmia!
We believe in self-organizing teams that own their ways of working. With Swarmia, teams already get full visibility into their process and can identify potential improvements — but transparency alone is not enough to become better and stronger as a team. Working Agreements is a powerful new feature that helps teams continuously improve with clear goals and consistent execution. Our first iteration includes features to manage the amount of work in progress and the cycle time of Pull Requests.
Managing the amount of work in progress and reviewing code without delay are some of the best ways for teams to improve their speed and focus. Our first Working Agreements allow teams to set work-in-progress limits for issues and Pull Requests, and to set a limit for Pull Request age.
Ready to jump in? Why not have a conversation with your team and head over to the new Working Agreements area in the app to get started.
Working Agreements are simple to configure and adopt, and insights about the Working Agreement as well as details about recent exceptions are clearly visible in the UI.
Finally, the daily Slack notification shows how the team is doing with their Working Agreements, helping teams adopt new habits with immediate feedback. If you haven't enabled Slack notifications for your team yet, now is a good time to do it!
What Working Agreements does your team use, or would find useful? We have lots of ideas about what to do next, but we'd like to hear from you.
The new Working Agreements feature is due for release in the coming days. Meanwhile, enjoy some new Insights about cycle time!
As mentioned in the previous feature update, managing the amount of work in progress is a great way to get work done faster.
New Cycle Time Insights plots completed issues on a timeline and shows how long they were open. The scatter plot makes it easy to identify outliers and trends, and drill down on individual issues.
Can you find correlations between the amount of work in progress and cycle time for your team?
Managing the amount of work in progress is one of the best ways for a team to improve focus and get work done faster.
Flow Insights plots the number of open Pull Requests, Epics, Stories and Tasks on a timeline, helping teams understand how much work they have on their plate at a given time.
Lots of Work in Progress usually correlates with longer cycle time and intermittent progress, which is something you can identify in Work Log. What correlations can you find?
Work continues on the Insights product area. This week we are adding Quality Insights to help teams stay on top of their Continuous Integration pipelines, and working on all new Insights about flow.
In addition to flaky builds, Continuous Integration Insights has a new tab that plots build times on a timeline. Drill down to a given day to see the average build runtimes and the number of builds.
Coming soon: Controlling the amount of unfinished work is a great way to stay focused and improve flow. Find out next week how we can help teams locate bottlenecks and understand how much work they have on their plate!
We're starting to develop a new product area called Insights to help teams form a holistic view of their ways of working. The first Insights are about quality: bugs and continuous integration.
Bug Insights shows the volume of bugs on a timeline and how many bugs you are opening and closing on a daily basis, based on your team's Jira data.
Continuous Integration Insights plots the daily percentage of flaky builds on a timeline. You can drill down to a given day to see how many builds were flaky and how much time was wasted waiting for them to complete.
Next up: build duration. Stay tuned, and don't forget to let us know what you think!