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
  • Setup
  • Using initiatives
  • Analyzing activity patterns
  • Initiative lifetime

Was this helpful?

Deliver strategic initiatives

Set up your initiatives to enable visibility beyond team-level work.

PreviousCommon problems with balancing engineering investmentNextForecasting initiatives

Last updated 1 day ago

Was this helpful?

Initiatives give you a high-level view of strategic, cross-team projects that can take months—or even years—to deliver. These projects are often hard to track with engineering tools because they’re spread across different boards and teams in your issue tracker. Swarmia consolidates all that information into a single view so you never lose focus of the bigger picture.

Initiatives show the big picture:

  • What has been already done and what is next

  • Is something stuck at the moment or at risk of getting dropped

  • How many teams and people are working on the initiative

  • Which team is driving the effort

Setup

  1. Add a new initiative or import an existing one from Jira

  2. Provide the initiative's basic information and link any relevant resource to it. You can provide the initiative's target start and end dates, but they are not required.

  3. By setting up your automated issue filters, you can assign work to your initiative based on certain criteria. We support a variety of filter options for issue data.

Using initiatives

The initiatives listing view allows for a top-level overview of all ongoing initiatives within the organization. From here, you can dive deep into initiatives that need steering.

For each initiative following attributes are displayed:

  • In progress time of how long an initiative has been ongoing since the first activity

  • Health badge displaying if the initiative is on track, idle, or at risk. The health is based on when the initiative had the latest activity:

    • On track when the initiative has had activity within four days

    • Idle if there has not been activity for four days

    • At risk if there has not been activity for over two weeks

  • Progress bar displaying the completed vs total of planned issues within an initiative and its child issues

  • Start date displaying the planned or first activity date

  • Target date displaying the planned target date or the last activity date for completed initiatives

Analyzing activity patterns

The detailed initiative view is used to inspect the initiative's progress, find any possible bottlenecks, showcase the contributors, and display the planned work to be started. Below are some things that can be inspected from the view.

Each dot in the activity timeline represents the volume of activity on a particular day or week. One of the best indicators of a stuck or blocked initiative is long periods of inactivity. When you spot long periods of inactivity, you can investigate further why work might be blocked. It’s possible to expand individual rows in the timeline to drill deeper into specific issues. You can also click on each dot on the timeline to see all contributors that happened on that day or week as a list. This way, you can pinpoint specific issues and unblock the work.

The mismatch between planned completion date and unstarted work and inactivity. An initiative might contain subtasks that are idle and have not had steady activity lately or the initial plan has been too ambitious.

Drill down to individual issues and inspect their progress

The data in this view can be used to gain insights into the work being done towards an initiative. If your initiative seems to be at risk of getting stuck, you can start conversations with your team to make steady progress.

Initiative lifetime

Navigate to

The calculation of an initiative's lifetime differs from . The initiative counts events when marking an issue as completed or when merging the first pull request associated with that initiative. Consequently, both the first and last activities of the initiative will be counted from that point onward.

Initiatives
the issue's lifetime
From the activity tooltip, you can see the ratio of done work for the time period
Swarmia - Creating an initative
Swarmia - Listing initiatives
Swarmia - Initiative overview
Swarmia - Initiative work explorer
Swarmia - Initiative activities tooltip