# Use cases

- [Improve pull request flow](/use-cases/improve-pull-request-flow.md): Get visibility into your team’s pull requests and the contributing factors behind cycle time: the number of pull requests in progress, batch size, and review time.
- [Pull request insights](/use-cases/improve-pull-request-flow/pull-request-insights.md): Diagnose cycle time issues, decrease review time and improve pull request workflow with Swarmia's pull request insights.
- [Reducing pull request cycle time](/use-cases/improve-pull-request-flow/reducing-pull-request-cycle-time.md): Get pull requests through faster with Swarmia's insights and working agreements around cycle time.
- [Review code faster](/use-cases/improve-pull-request-flow/review-code-faster.md): Code rarely ages well, and merging doesn’t get any easier over time. Here's how Swarmia helps your team get pull requests through faster.
- [Managing pull requests in progress with the Pull Request view](/use-cases/improve-pull-request-flow/managing-pull-requests-in-progress-with-the-pull-request-view.md): See all open pull requests and where they are going in a team context.
- [Diagnosing low pull request throughput](/use-cases/improve-pull-request-flow/diagnosing-low-pull-request-throughput.md): Throughput is more difficult to improve than for example cycle time, since it reflects the team's overall situation rather than just the process.
- [Analyzing pull request batch size](/use-cases/improve-pull-request-flow/analyzing-pull-request-batch-size.md): Batch size measures how much work is bundled up in a change. Swarmia offers tools for evaluating pull request batch size by looking at the total amount of changes.
- [Improve your team's focus](/use-cases/improve-your-teams-focus.md)
- [Optimizing issue cycle time](/use-cases/improve-your-teams-focus/optimizing-issue-cycle-time.md): Practical tips and best practices for improving your focus and structuring work to reduce issue cycle times.
- [Analyzing activity patterns on work log](/use-cases/improve-your-teams-focus/analyzing-the-activity-patterns-on-work-log.md)
- [Grouping activity on the work log view](/use-cases/improve-your-teams-focus/grouping-activity-on-the-work-log-view.md): Swarmia's work log can give you the most holistic picture to your work in progress. In this article we explain how activity gets grouped on the work log.
- [Focus summary](/use-cases/improve-your-teams-focus/focus-summary.md): The focus summary allows you to easily explore what your teams and organization are spending the most effort (FTEs) on.
- [Balance engineering investments](/use-cases/balance-engineering-investments.md): Analyze team focus, improve time allocation and boost focus on top priorities
- [Activity and effort-based models](/use-cases/balance-engineering-investments/activity-and-effort-based-models.md): Swarmia supports two different models to measure the work: activity-based and effort-based
- [Categorizing work](/use-cases/balance-engineering-investments/categorizing-work.md): Configure custom categories and and improve the categorization rate.
- [Common problems with balancing engineering investment](/use-cases/balance-engineering-investments/common-problems-with-balancing-engineering-investment.md): Swarmia investment balance helps you answer many questions that engineering organisations struggle with.
- [Deliver strategic initiatives](/use-cases/deliver-strategic-initiatives.md): Set up your initiatives to enable visibility beyond team-level work.
- [Forecasting initiatives](/use-cases/deliver-strategic-initiatives/forecasting-initiatives.md): Estimate how long initiatives will take.
- [Capitalize software development costs](/use-cases/capitalize-software-development-costs.md): Use developer activity data from Swarmia to generate capitalization reports and blend with cost data.
- [Timesheets](/use-cases/capitalize-software-development-costs/timesheets.md): Timesheets help your organization record, approve, and export hours at the daily and individual level without manual tracking during work.
- [Run developer experience surveys](/use-cases/run-developer-experience-surveys.md): See what truly affects developer experience and productivity by viewing relevant survey results alongside your system data.
- [Creating a survey](/use-cases/run-developer-experience-surveys/creating-a-survey.md): Improve developer experience by collecting insights directly from your engineers at scale. Identify patterns and turn them into actions.
- [Managing surveys](/use-cases/run-developer-experience-surveys/managing-surveys.md): You can create, preview, duplicate, close, and delete surveys.
- [Viewing and sharing survey results](/use-cases/run-developer-experience-surveys/viewing-and-sharing-survey-results.md): After a survey ends, you can review the results, publish them to your teams, or export them
- [How we show your survey responses](/use-cases/run-developer-experience-surveys/how-we-show-your-survey-responses.md): Responses are reported by team. You can choose whether to show your name in comments.
- [Survey communication guide and templates](/use-cases/run-developer-experience-surveys/survey-communication-guide-and-templates.md): You can use this messaging sequence and templates to communicate your developer experience survey to your teams.
- [Measure the productivity impact of AI tools](/use-cases/measure-the-productivity-impact-of-ai-tools.md): Combine developer experience surveys, adoption metrics, and usage patterns to understand how AI coding tools play into your software organization’s productivity.
- [AI adoption metrics](/use-cases/measure-the-productivity-impact-of-ai-tools/ai-adoption-metrics.md): Track GitHub Copilo, Cursor, and Claude Code licenses and adoption across your teams over time
- [AI impact on PR metrics](/use-cases/measure-the-productivity-impact-of-ai-tools/ai-impact-on-pr-metrics.md): See how pull requests assisted by different AI coding tools — or no AI tools — perform across metrics like throughput, cycle time, batch size, and review time.
- [AI coding agent metrics](/use-cases/measure-the-productivity-impact-of-ai-tools/ai-agent-metrics.md): Gain visibility into the pull requests assisted by different AI coding agents and how they perform across metrics like throughput, merge percentage, and batch size.
- [GitHub Copilot activity breakdown](/use-cases/measure-the-productivity-impact-of-ai-tools/github-copilot-activity-breakdown.md): See detailed GitHub Copilot activity patterns across teams, features, models, editors, and programming languages
- [Cursor activity breakdown](/use-cases/measure-the-productivity-impact-of-ai-tools/cursor-activity-breakdown.md): See detailed Cursor activity patterns across teams and modes
- [Claude Code activity breakdown](/use-cases/measure-the-productivity-impact-of-ai-tools/claude-code-activity-breakdown.md): See detailed Claude Code activity patterns across teams and modes
- [Track DORA metrics](/use-cases/track-dora-metrics.md): Analyze deployment frequency and quality across your entire organization in Swarmia.
- [Automatic change failure detection](/use-cases/track-dora-metrics/automatic-change-failure-detection.md): Automatically detect DORA change failures from application version rollback, pull request reverts, and advanced hotfix filters.
- [How Swarmia links PRs to deployments](/use-cases/track-dora-metrics/how-swarmia-links-prs-to-deployments.md): Linked PRs are used to calculate change lead time and time to deploy. The are also used to determine who owns the deployment.
- [Coach software developers](/use-cases/coach-software-developers.md): Visualize engineering work with Developer Overview
- [Improve code quality](/use-cases/improve-code-quality.md): Build better quality products, reduce technical debt, and implement development practices that scale as your team grows
- [Get visibility into your CI pipeline](/use-cases/get-visibility-into-your-ci-pipeline.md): Swarmia provides you with the most important CI metrics for tracking your CI health