Hurdle Docs
Go back to Hurdle.dev
  • Introducing Hurdle
  • Integrated or standalone
  • Getting started
    • Workspace setup
      • General settings
      • Managing users
      • Issues
      • Estimates
      • Backlog
      • Workstreams
      • Sprints
    • Integrating with Jira
      • Enabling the integration
      • Field mapping
      • User mapping
      • Common questions
  • Using Hurdle
    • Managing work
      • Projects
      • Issues and subtasks
      • Triage queue
      • Views and filters
    • Backlog refinement
      • Backlog conditions
      • Workstreams
      • Prioritization
    • Sprint planning and tracking
      • Sprint settings
      • Automated planner
      • Adding and removing issues
      • Starting a sprint
      • Active sprints
      • Ending a sprint
      • Completed sprints
Powered by GitBook
On this page
  • Sprint settings
  • Team availability
  1. Using Hurdle
  2. Sprint planning and tracking

Sprint settings

Set team velocity, capacity and determine which issues should carry from sprint to sprint.

PreviousSprint planning and trackingNextAutomated planner

Last updated 1 year ago

The for each sprint series can be set under Settings > Workspace > Sprints.

Each sprint within a series will inherit the settings of the series. Primary settings for and can be overwritten for individual sprints within a series in the planner.

Sprint settings

In settings, you can set your team's capacity (in points or time) for the sprint, and determine which issues from the previous sprint should be carried over into the upcoming sprint.

By default, these settings will match the , but they can be changed for each sprint within the series.

Capacity

Carryover

Carryover determines which issues should be carried over from the previous sprint into the sprint that's being planned. Typically, issues that have not yet been started and those that are in progress are carried over.

Carryover is based on the current status of issues at the time of planning.

Team availability

For each sprint, you're also able to set the availability of each team member. The amount of points available for each member is based on overall team capacity/velocity and their availability.

For example, in a 10-day sprint, someone who has 10 full days available will have twice as much capacity as someone who has 5 days available.

Setting team availability

Prior to a sprint beginning, each team member can set their availability by going to the planning screen for the sprint. After they've inputted the number of days they're available, they can click on the status toggle to change it to Confirmed.

Team leads can also set the available days for each team member.

Nudging team members

If a team member has not confirmed their availability for an upcoming sprint, they can be nudged to do so by clicking on the email icon. When nudged, the team member will receive an email asking them to enter and confirm their availability for that specific sprint.

Adding and removing users

By default, every user in your workspace will be part of each sprint and sprint series. Users can be removed from individual sprints or the entire sprint series by clicking on the additional options.

Removed users can be added back at any time.

If a user is unavailable for a specific sprint and not being removed from the entire series, we recommend setting their capacity to 0 days instead of removing them from the sprint.

Capacity determines the total amount of work your entire team can take on over the upcoming sprint. The unit (points or time) for team capacity are the same as the used across your workspace.

When a sprint series is active, this value will be automatically calculated based on the actual amount of work your team has completed in previous sprints. The calculation method can be set in the .

estimate units
sprint series settings
primary configuration
team capacity
carryover tickets
sprint series settings