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
  • Unhealthy patterns
  • Working alone
  • Siloed work
  • Too much reactive work
  • Multitasking and days without progress
  • Healthy patterns
  • Team collaboration
  • Increasing focus on the biggest priorities

Was this helpful?

  1. Improve your team's focus

Analyzing activity patterns on Work Log

PreviousOptimizing issue cycle timeNextGrouping activity on the Work Log view

Last updated 1 day ago

Was this helpful?

Work Log visualizes the various activities of your team. Knowing which work patterns to avoid and which to aim for helps teams improve their health and development speed.

Unhealthy patterns

Working alone

People tend to gravitate to working on their own things because it's easy and doesn't involve coordinating with others. However, great teams are built upon collaboration and sharing knowledge.

Look for epics, stories, or tasks where you can only see one contributor. Could they use a hand?

Being able to work on the same feature sets the bar higher for planning because you can't figure things out as you go. This is generally a good thing: better planning reduces wasteful rework, but it can feel painful at first.

Siloed work

Another form of siloing is when some people always gravitate to working together on the same features or when someone is stuck only fixing bugs or reviewing code.

Look for patterns in which individual contributors are only working on one kind of thing. In the example below, the bottom contributor is mainly reviewing code instead of a balanced mix of commits, pull requests, and reviews.

Too much reactive work

Housekeeping work is important to ensure the team's capability to deliver on roadmap work. But if priorities and focus are unclear, or the team is fighting fires, it can be easy to get lost in the weeds of ad hoc work.

If the work log is bottom-heavy with lots of reactive work (eg. bugs and tasks), try to correct the course by focusing more on high-impact stories and epics.

Is there a lot of bug-fixing work, and work that's not linked to any issues?

Multitasking and days without progress

We're encouraged to stop starting and start finishing, but something urgent always comes up. Even short disruptions can impair flow, and context switching is expensive.

Is the team getting interrupted or working on too many things at the same time? Or has the team a habit of creating larger commits and Pull Requests?

Healthy patterns

Team collaboration

Issues that the team collaborates on are more likely to be completed faster and are usually more fun to work on due to social interaction, knowledge sharing, and quicker reviews.

Look for stories with a high amount of collaborators, and continuous delivery (commits happening regularly every day).

Plan for collaboration (eg. when breaking work into tasks) to increase the odds of collaboration.

Increasing focus on the biggest priorities

Limiting the amount of work is another way to increase team collaboration, and complete batches of work faster. This helps drive focus which ensures the team can progress in their most important priorities.

Again, ensure the stories get continuous progress and little to no empty days. Additionally, look for a step pattern. If there is one, the team transitions well between stories and takes the time to finish work before jumping on to the next topic.

Sometimes it can be easier to analyze the step pattern on the high-level work log, where the work is aggregated on the weekly level.

Swarmia - Working alone in work log
Swarmia - Different activities in work log
Swarmia - Not linked issues in work log
Swarmia - Inactive days in work log
Swarmia - Good work habits in work log
Swarmia - Good focus in work log
Swarmia - Step pattern in high-level work log