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
    • Pull request exclusions
    • Issue tracker configuration
      • Jira configuration
      • Jira best practices
      • Linear configuration
    • 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
    • Retrospective guide
  • 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
  • Activity-based model
  • Effort-based model
  • Activities are based on team memberships
  • How work is grouped by category

Was this helpful?

  1. Balance engineering investments

Activity and effort-based models

Swarmia supports two different models to measure the work: activity-based and effort-based

PreviousBalance engineering investmentsNextCategorizing work

Last updated 21 days ago

Was this helpful?

Activity-based model

The activity-based model shows activity on pull requests and issues grouped by investment categories. The activity model includes both completed issues and merged pull requests.

Effort-based model

The effor-based model normalizes GitHub and issue tracker activities for each developer. Normalizing means Swarmia takes into account different coding and working styles. In practice, this means a developer can have a maximum of 1 FTE (full-time equivalent) in a month. The FTE is distributed across all issues and pull requests the developer has worked on during the month.

Activities are based on team memberships

If your team members have contributed towards issues belonging to other teams, be default also those issues will be visible in your team's investment balance. Your team is investing its time somewhere, and the report shows you where that investment goes, even if it's not for the things you might've expected. You can filter out these items by selecting Only work owned by team as shown in the image below.

How work is grouped by category

If multiple tasks belong to a bigger project, it's possible to have different investment categories assigned to each task and the project as a whole. In this case, we'll show each task in its respective category of work.

We start by looking at all contributions by all team members of the selected team, then determine the investment category based on

Then work is grouped by investment category (these categories are ).

the rules you've set up.
mutually exclusive and collectively exhaustive
Read more about how Swarmia measures developer effort.
Investment balance with "Only work owned by team" selected