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
  • Work better together
  • A multi-functional tool for continuous improvement
  • Get started with working agreements

Was this helpful?

  1. Continuous improvement

Working agreements

Working agreements help teams continuously improve with clear goals and consistent execution

PreviousGet visibility into your CI pipelineNextNotifications

Last updated 1 month ago

Was this helpful?

Work better together

We believe in self-organizing teams that own their ways of working. With Swarmia’s , and , you already get full visibility into your process and can identify potential improvements — but transparency alone is not enough to become better and stronger as a team.

You’re probably used to sitting down (or standing up!) together as a team and deciding to change something about how you’re working. Maybe this is something you do as a matter of process, for example, in a retrospective meeting every couple of weeks. Having retrospectives and systematically improving ways of working is something that all teams should do, but without considerable self-discipline and support from the organization, decisions to improve can end up being ignored or forgotten.

help you spring from idea to action, execute consistently, and form new habits as a team.

A multi-functional tool for continuous improvement

Some issues you can identify with Swarmia are clear-cut, while others have considerable nuance and complexity. For instance, code reviews are probably not slow because developers are lazy but because of deeper issues with focus or infrastructure. In cases like these, exceptions highlighted by working agreements are opportunities to dive deeper into the root causes and have meaningful conversations as a team. .

On the other hand, managing work in progress is widely recognized as the most critical driver of focused teams that deliver fast. Simply limiting the number of Stories, Tasks, or Epics the team can have on its plate at a given time is all but guaranteed to result in faster cycle times and better team dynamics.

Get started with working agreements

Ready to jump in? Why not have a conversation with your team about issues you’ve detected about team focus or Pull Request cycle times, and head over to the to get started!

After choosing what to improve and setting up the working agreement, you get insights about how you’re doing as well as a list of all exceptions from the past two weeks helping you pinpoint specific issues or discussions to have with the team.

Finally, the daily Slack digest keeps you up to date about progress and exceptions and helps your team stick to new habits. If you haven't enabled the daily Slack digest yet, !

now is a good time to do it
Pull Request Dashboard
Work Log,
Insights
Swarmia's working agreements
You can read more about why and how to review code faster here
working agreements
Explore working agreements and decide what to improve
Set up working agreements and see how you’re doing
Daily feedback helps stick to new habits