We’ve released Time-Based Comparisons, which let you compare productivity before/after a key event. Examples of major events that you can measure with this feature include acquisitions, layoffs, leadership changes, and adopting new tools.

To get started, go to the Comparisons tab and click Create Comparison. When setting up the comparison, select Before vs. after an event, which will allow you to define a new key event and select the groups that you want to compare.

If you have any questions or would like help setting up a time-based comparison, feel free to reach out to us at support@software.com.

Based on feedback from our community, we’ve improved our Features per Developer metric to better standardize industry benchmarks and provide better accuracy when comparing groups within your organization, such as developers using vs. not using GitHub Copilot.

As part of this update, the developer count will include contributors who created a pull request in the last 90 days. Previously, the developer count included any contributor who created or reviewed a pull request in the last 30 days.

Extending the activity window from 30 to 90 days accounts for seasonality, providing a more stable representation of your organization’s size over time. Developers who leave your organization are counted towards historical activity, but immediately removed from your developer count going forward.

Cost per feature still includes contributors who created or reviewed code in the last 90 days—to more precisely capture the costs associated with developing, reviewing, and delivering features. Development costs are calculated by multiplying a group’s cost per contributor by the count of developers and reviewers within the group.

You may notice small changes to your metrics and global benchmarks. You can read more about this change in our documentation, or feel free to reach out to us with any questions at support@software.com.

We’ve improved our feature calculations to automatically ignore pull requests in development workflows—such as dependency updates, back merges, and releases—that are not representative of developer productivity. These improvements have been requested by customers. As a result of this update, you may see a slight decrease in features per engineer, and industry benchmarks will be more accurate.

A pull request is excluded from your metrics if it meets any of the following criteria:

• It is authored by a bot (e.g. a dependency update)
• The head branch is the default branch (e.g. a back merge to sync changes from default into a development branch)
• It does not include any unique commits that haven’t already existed in a previous pull request (e.g. merging a release branch into main)
• More than three authors merged a pull request into the head branch (e.g. a long-lived feature branch)

You can review the list of pull requests that are included/excluded in our definitions by hovering over a data point and viewing more pull requests in the flyout.

Based on feedback from our community, we’ve made several improvements to our active engineers algorithm:

Improvements

• We’ve updated our active engineers definition to include users in your Git organization who have contributed or reviewed code in the last 30 days. Previously, only users who created pull requests were included. Users who exclusively review pull requests — such as team managers — will now be included in the active engineer count.

Bug fixes

• We’ve updated several queries to ensure that a 30-day rolling average of active engineers is always used. Previously, an active engineer may have been excluded if they did not create a pull request in a specific week.
• We’ve added better automatic detection for pull requests authored by bots, such as Dependabot updates. As a result, you may notice a decrease in your features per engineer metric. As a reminder, you can always manually filter out bots under Settings / Git Users.

Today we’re releasing a small but helpful improvement to our app for Slack. In our latest update, you can now send notifications — including daily and weekly digests — to private channels in your workspace.

To get started, you’ll need to approve new permissions for our Slack app (it takes just a few seconds). Head over to your team’s Connected Apps in your organization’s Settings and click Upgrade Slack.

⚡ How to send notifications

To send notifications to a private slack channel, you will need to first add our bot to the channel.

1. Select the channel where you want to send notifications.
2. In the message field, type “@Software.com” and hit send. Follow the prompts in Slack to invite our bot to this channel.
3. Visit your organization settings in the Software.com web app. In the Notifications section, refresh the dropdown menu and select your private channel.

You can learn more about our app in the Slack marketplace.

We recently released Feature Breakdowns to give you more insight into what work is categorized as new, churn, and refactor during a given time period. You can access breakdowns by clicking on a data point in the Feature Breakdown chart.

💡 As a quick refresher, features are broken down into three types:

• New: new code added
• Churn: code reworked less than 21 days after being merged
• Refactor: code reworked more than 21 days after being merged

Based on feedback from our community, we’ve slightly modified how these calculations work. Instead of aggregating line changes over a time period and then multiplying the ratios by the total number of features, we are now averaging the breakdown per feature. As a result, you will likely see a lower number for % New Features vs. Rework. Our industry benchmarks have been adjusted accordingly.

If you have any questions, please don’t hesitate to reach out to us at support@software.com.

Our new Jira integration provides you with a more complete picture of lead time, all the way from issue in progress to changes deployed. When you connect Jira, we automatically link your team’s pull requests to issues, giving you visibility into time spent on changes even before the first commit.

✨  What’s new?

• Measure lead time from issue in progress to deploy, for end-to-end visibility into team efficiency.
• Get a more complete view of development time, the time between starting an issue to opening a pull request.
• No configuration required. We automatically link Jira issues and pull requests if a pull request name contains a project prefix and number associated with a Jira issue (e.g. JRA-123).

⚡ Get started with Jira

You can connect Jira from the Atlassian marketplace in just a few minutes, or learn more in our documentation. You will be able to choose your workspace and review permissions before installing the app.

We’ve redesigned our Slack app from the ground up to elevate your team’s collaboration and productivity. With new features — like reminders for blocked pull requests and previews of upcoming deployments — you can keep your team on track and stay on top of work that’s in-flight.

It’s also now easier than ever to try out our Slack integration. Starting today, you can find our app in the official Slack marketplace.

✨ What’s new

• Deployment previews: When you’re ready to ship, send a preview of your upcoming deployments to team members in Slack.
• Digests: Share updates with your team and see how your team is tracking against your working agreements.
• Reminders: Get automated reminders when pull requests waiting on review, approval, merge, and deployment do not meet your working agreements.
• Async reviews: Start group code reviews and create new Slack channels for your pull requests to collect and share feedback during the code review process.
• Standup bot: Automate daily standup by generating a message that recaps your recently closed and currently open pull requests.

⚡ Get started with Slack

You can learn more about our app for Slack in the marketplace.

We’re starting off the year with new insights into lead time to help you understand how long it takes you to make product changes. With the lead time dashboard, you can answer questions like:

• How are we performing relative to before?
• Where are there bottlenecks in our development process?
• Which changes took us the longest to make?
• Is this increase in our lead time caused by longer review and deploy times or an increase in our work load?

✨  What’s new?

• Breakdowns of lead time by stage, team, repository, and label to help you identify bottlenecks.
• Comparisons to previous period to see how your team is trending.
• Related metrics, such as review turnaround time and time to deploy, to see what’s impacting lead time.
• Insight into which changes took the longest to make, organized by pull request.

👋  Get in touch

We’d love to hear your feedback on our new lead time insights. Otherwise, stay tuned — we have some exciting updates in the weeks ahead.

Our latest update helps you stay on top of work that’s ready to be deployed and prevent large backlogs of changes. With new deployment metrics and more powerful Slack notifications, you can make your team’s deployments faster, easier, and more frequent.

✨  What’s new?

• Keep a pulse on the overall health of your deployment process with new summary metrics. Get insight into how long it takes to deploy changes, the number of recent deployments, and the success rate of those deployments.
• Track upcoming deployments with a summary of pull requests ready to ship, organized by repository and sorted by the maximum age of changes waiting to be deployed.
• Notify your team team of changes that need to be deployed with deployment previews in Slack.
• Prevent changes from becoming stale by setting up notifications when changes are not deployed within some number of days of being merged.
• View recent deployments to keep track of previously released changes.

🔷  Get started with previews in Slack

When you send a preview of a deployment to Slack, we’ll share a summary of the pull requests ready to ship and their authors. Head over to your Upcoming Deployments and select View to open an information panel, where you can then select the channel you want to notify.

👋  Get in touch

Need help connecting Slack or configuring deployments? You can find some time to chat with us and we’ll walk you through how you can use the Ready to Deploy feature to improve your team’s velocity.