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

Was this helpful?

Last updated 1 month ago

Was this helpful?

What is FTE?

A full-time equivalent (FTE) is a unit of measurement used to determine the number of full-time hours worked by all employees in an organization. If your organization considers 160 hours a full-time work month, an employee working 160 hours per month would have an FTE of 1.0. In contrast, a part-time employee working only 80 hours per month would have an FTE of 0.5 — which shows that their hours worked are equivalent to half of a full-time employee.

In Swarmia, FTEs are measured in months.

How is effort measured in Swarmia?

Each developer is allocated one FTE per month. Swarmia considers GitHub and issue tracker activities to distribute this monthly effort (FTE) across the issues and pull requests the developer has worked on:

  • Commits created

  • Pull requests opened

  • Pull request reviews and comments

Activities are weighted, with pull requests and commits counted more heavily than reviews and comments.

We calculate the sum of these data points for a given month and then normalize it for each developer. Normalizing means we take into account different coding and working styles. In practice, this means a developer can have a maximum of 1 FTE in a month, it is distributed for all issues and pull requests the developer has worked on during the month.

We adjust the allocated FTE for lengthy periods of inactivity and, if your HR system is connected with Swarmia, for logged time off periods.

Here’s an illustrative example of two developers and what their monthly calculations may look like.

There are several ways we improve the accuracy of effort calculation:

  • Contributors with little to no activity are excluded.

  • All bots and events related to bot-authored pull requests are excluded.

  • The current month's effort is adjusted. For example, if today is the 15th day, Swarmia attributes only 0.5 FTE for the current month.

    • Each author's FTE is adjusted based on their available working days in the month.

    • Time offs can be specified in either days or hours:

      • When specified in days, each day counts as a full day off

      • When specified in hours, any partial day off (including half-days) is counted as a full day off

    • For example, if there are 20 working days in a month and a developer has 15 work days off, their total FTE would be 0.25 (calculated as (20 - 15) / 20).

    • Weekends within the time off periods are skipped.

    • Public holidays are not currently considered in the calculations.

  • The effort data will be refreshed daily for the past two months. The older data is refreshed weekly.

Only contributors who have a linked GitHub user are taken into account. You can .

Contributor's effort can be adjusted or even excluded from calculation in .

If , then vacations, sick leaves, and time offs are taken into account:

  1. Metrics & definitions

Developer effort (FTEs)

Swarmia measures developer effort in FTEs (full-time equivalent).

PreviousDefining issue lifecycle and cycle timeNextDORA metrics
  • What is FTE?
  • How is effort measured in Swarmia?
review your contributors in the app settings
app settings page
HR system is connected to Swarmia