LogoLogo
Book a demoLog in
  • Swarmia documentation
  • Getting started
    • Get started in 15 minutes
    • Integrations
      • GitHub
        • GitHub Enterprise Server
        • Multiple GitHub organizations
        • Forked repositories
        • Troubleshooting
          • Reinstalling the Swarmia GitHub app
          • Updating app permissions
          • Installing Swarmia outside of GitHub Marketplace
      • Jira
        • Jira Server and Jira Data Center
        • Multiple Jira organizations
      • Linear
        • Private Linear teams
        • Disconnect Linear
      • Slack
        • Private Slack channels
      • Authentication
        • Google Single Sign-On
          • Frequently asked questions
        • Okta Single Sign-On
      • HR systems
      • Data export
        • Data cloud
        • Export data as a CSV file
      • Other integrations
        • Other issue tracker integrations
        • Other source code hosting integrations
  • Configuration and data quality
    • Teams & members
      • Creating & managing teams
        • Teams API
      • Contributors
      • Roles and permissions
      • Inviting team members
    • Issue tracker configuration
      • Jira configuration
      • Jira best practices
      • Linear configuration
    • Pull request exclusions
    • Linking pull requests to issues
    • Investment categories
    • Deployments
      • Generate deployments from merged pull requests
      • Generate deployments from GitHub deployments
      • Generate deployments from GitHub checks
      • Generate deployments via the API
        • Generate deployments for monorepos via the API
    • Sprint configuration
  • Use cases
    • Improve pull request flow
      • Pull request insights
      • Reducing pull request cycle time
      • Review code faster
      • Managing pull requests in progress with the Pull Request view
      • Diagnosing low pull request throughput
      • Analyzing pull request batch size
  • Improve your team's focus
    • Optimizing issue cycle time
    • Analyzing activity patterns on Work Log
    • Grouping activity on the Work Log view
    • Focus summary
  • Balance engineering investments
    • Activity and effort-based models
    • Categorizing work
    • Common problems with balancing engineering investment
  • Deliver strategic initiatives
    • Forecasting initiatives
  • Capitalize software development costs
  • Run developer experience surveys
    • Creating a survey
    • Managing surveys
    • Viewing and sharing survey results
    • How we show your survey responses
    • Survey communication guide and templates
  • Track DORA metrics
    • Automatic change failure detection
    • How Swarmia links PRs to deployments
  • Coach software developers
  • Get visibility into your CI pipeline
  • Continuous improvement
    • Working agreements
  • Notifications
    • Team notifications
    • Personal notifications
  • Retrospectives with Swarmia
  • Metrics & definitions
    • Pull request cycle time
      • What's the difference between "Change lead time" and "Pull request cycle time" metrics in Swarmia?
    • Issue cycle time
      • Defining issue lifecycle and cycle time
    • Developer effort (FTEs)
  • DORA metrics
    • Change lead time
    • Deployment frequency
    • Mean time to recovery
    • Change failure rate
  • Throughput
  • Time to deploy
  • Batch size
  • Flow efficiency
  • Scope creep
  • Sprints
  • Frequently asked questions
    • How do you treat weekends in metrics?
    • Tracking squashed commits
    • How do merge queues affect my metrics?
    • Why is my commit not visible in Swarmia?
    • How do I account for people leaving my organization?
  • Resources
    • Security & data retention
      • Data security
      • Data access
      • Swarmia IP Addresses
      • Single Sign-On (SSO) / SAML
      • Can I get a copy of the SOC 2 Type II audit report?
      • Deleting your organization
  • Pricing & plans
    • Compare plans
    • Free plan
    • Do I need a credit card to start a free trial?
    • What are the differences between the individual modules and the standard plan?
    • How do you determine the number of developers for billing?
    • What happens to customers with the Lite plan after the December 2024 pricing and plan change?
  • Changelog
On this page
  • Related metrics
  • Initiative lifetime
  • Summary
  • Example
  • Why it matters
  • How to use it
  • Where to find it

Was this helpful?

Flow efficiency

The flow efficiency of an issue is the percentage of days when the issue was actively worked on compared to its whole lifetime.

Related metrics

The lifetime of an issue is the amount of time between its first and last activity, according to merged data from your issue tracker and your version control system.

The active days of is the number of days on which an issue had some activity, either on GitHub or your issue tracker.

Issue activity includes all events that can be tied to the issue in question, such as commits, pull requests, and reviews. Issue status changes also count as activity.

Flow efficiency does not count weekends against the efficiency calculation, issue cycle time does include weekends.

Initiative lifetime

The calculation of an initiative's lifetime differs from the issue one. The initiative counts events when marking an issue as completed or when merging the first pull request associated with that initiative. Consequently, both the first and last activities of the initiative will be counted from that point onward.

Summary

Flow efficiency measures the share of active days during the lifetime of an issue. Lifetime includes only business days (weekdays, excluding weekends).

Example

If an issue from your issue tracker was opened on May 1st and completed on June 6th, we would first calculate that it had a lifetime of 36 calendar days. However, for the purpose of flow efficiency, we consider only business days (weekdays, excluding weekends). Suppose there are 26 business days in that timeframe. Then, we look at how many of those days had recorded activity—either from child issue movement or GitHub activity—to determine the number of active days.

Let’s say there were 10 active business days. The flow efficiency would then be calculated as:

(10 active days / 26 business days) × 100 = 38%

Why it matters

Low flow efficiency also indicates problems with focus and context switching, which can negatively impact developer experience. This also means you likely could have shipped sooner, and delivered value to your users more quickly.

How to use it

If you notice an issue has a flow efficiency of less than 80%, have a discussion with your team about what caused that. Was it because there were too many other work items in progress? Was the initial piece of work not well defined, which led to bottlenecks and scope creep? Depending on the answer, you can then take steps to improve in future cycles. There could also be an opportunity here to adopt a working agreement for your team to help drive higher flow efficiency.

Where to find it

You can find flow efficiency (and other flow metrics) by opening an issue popup anywhere in Swarmia where you see the name of an issue.

PreviousBatch sizeNextScope creep

Last updated 19 days ago

Was this helpful?