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
        • Jira best practices
        • 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
    • Creating & managing teams
      • Teams API
    • Managing users and roles
    • Organization settings
      • Jira setup
      • Data quality
        • Pull request data quality
        • Linking pull requests to issues
      • Investment balance
      • 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
    • Team settings
      • Mapping work to your team
      • Sprints
      • Team notifications
    • Notifications
      • Personal notifications
  • 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
  • Working agreements
    • Set up working agreements
  • 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
  • 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
  • Summary
  • Example
  • Why it matters
  • How to use it
  • Where to find it

Was this helpful?

Scope creep

Scope creep measures the amount of work added to an issue while it was in progress.

Summary

Scope creep is measured by the amount of child issues created after an issue has first moved to an 'in progress' status. Scope creep is calculated as the ratio of these created issues and the original issues in the story.

Example

A story that had 8 issues when started and 12 issues when completed has a scope creep of (12-8)/8 = 50%

Why it matters

Scope creep is an indicator of planning quality. Some amount of scope creep is to be expected, but a high scope creep starts to indicate a problem with the planning process.

How to use it

Look for issues with unusual amounts of scope creep (significant outliers) to start discussions while the issue is still fresh in memory, and analyze the subtasks using the issue popup. Was this expected or something that could have been prevented? Is there something that the team can learn from this? Which subtasks were added after starting, or which of them took the longest?

Also, be on the lookout for consistently high scope creep (at least 50% on average): this might indicate a more systemic problem with the planning process. Perhaps you need to put more emphasis into story planning to avoid the same surprises in scope. Are you consistently forgetting some types of tasks, like documentation or instrumentation? Planning templates can solve some of these problems.

Where to find it

You can find scope creep by clicking open an issue popup anywhere in Swarmia where you see the name of an issue.

PreviousFlow efficiencyNextFrequently asked questions

Last updated 1 month ago

Was this helpful?