Help Center
Help Center
  • Getting Started
    • What is Haystack?
    • Quick Start
      • Account Setup
      • Roles
        • For Executives
        • For Managers
        • For Product
  • Setup
    • Integrations
      • Jira
      • GitHub Cloud
      • GitHub Enterprise
      • GitLab
      • Bitbucket
      • Slack
    • Organization
      • Investments
      • Deployments
      • Invite users
      • Exclusions
    • Teams
      • Map members
      • Sprint success metric
      • Capacity
      • Alerts
      • SLAs
      • Risks
  • Features
    • Issues
    • Pull Requests
    • Epics
    • Retrospective
    • Release Notes
    • Investments
    • Alerts
    • Customizable Widgets
    • Flexible Reports
    • Team Metrics
    • List of All Metrics
    • API
    • Embedded reports
  • Admin
    • Security & Privacy
    • Data Sync
      • How to setup faster data sync for JIRA?
  • FAQ
    • Can I track Dora metrics?
    • What is Status Category?
  • Guides
    • First Principles of Engineering Metrics
    • Engineering Metrics (Video Series)
    • How to Improve Quality?
    • Sprint Planning
    • Daily Standups
    • Retrospectives
    • Identify Bottlenecks
  • Other
    • Changelog
Powered by GitBook
On this page
  • Basics
  • What will be impacted
  • Setup
  • FAQ

Was this helpful?

  1. Setup
  2. Teams

Sprint success metric

Last updated 5 months ago

Was this helpful?

Setup a key metric for your team that helps you evaluate the success of a sprint.

Basics

Haystack provides two options as a sprint success metric:

  1. Completion Rate (default): the percentage of work completed against the total sprint scope, including any scope changes during the sprint.

  2. Commitment Reliability: the percentage of work completed from the initial sprint plan, excluding any scope changes mid-sprint. Choose this metric if you want to:

    1. Ensure team stays on track with original sprint commitments

    2. Identify gaps between planned and completed work

What will be impacted

Based on your sprint success metric selected in settings, you will see changes in all sprint-related pages: Issues, Retro, Sprint review.

Setup

  3. Click Save.

FAQ

Does the 'Sprint Success Metric' apply retroactively?

Yes, metric will be applied retroactively to all past sprints for the team.

Do issues removed mid-sprint impact commitment reliability?

Yes, removing issues mid-sprint is considered a scope change and will affect the sprint reliability metric.

Does a high Commitment Reliability indicate a successful sprint?

Not necessarily. While high Commitment Reliability indicates good planning, factors like long-term goals, value delivered, and team capacity are equally important.

When should Commitment Reliability be used over Completion Rate?

Commitment Reliability is ideal for improving sprint planning accuracy, assessing adherence to initial commitments, reducing scope changes, and enhancing delivery predictability.

Head to the page via the Settings icon on the left sidebar

Navigate to '' settings and select metric in "Sprint success metric" section:

Teams Settings
Board
Sprint success metric is shown in overview section
Sprint success metric is shown in retros page table
Sprint success metric is shown in retros page table